NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2025-67731: Servify-express rate limit issue

highCVSS 4.0 8.7GHSA-qgc4-8p88-4w7m

Impact The Express server uses express.json() without a size limit, which can allow attackers to send extremely large request bodies. This may lead to excessive memory usage, degraded performance, or process crashes, resulting in a Denial of Service (DoS). Any application using the JSON parser without limits and exposed to untrusted clients is affected.

Published Dec 11, 2025 · Updated Dec 12, 2025

Affected packages

servify-express

Ecosystem
npm
Affected
<= 1.1
Fixed in
1.2
Check
npm ls servify-express

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

The Express server uses express.json() without a size limit, which can allow attackers to send extremely large request bodies. This may lead to excessive memory usage, degraded performance, or process crashes, resulting in a Denial of Service (DoS). Any application using the JSON parser without limits and exposed to untrusted clients is affected.

Patches

This issue is not a flaw in Express itself but in configuration. Users should set a request-size limit when enabling the JSON body parser. For example: app.use(express.json({ limit: "100kb" }));

Workarounds

Users can mitigate the issue without upgrading by:

  • Adding a limit option to the JSON parser
  • Implementing rate limiting at the application or reverse-proxy level
  • Rejecting unusually large requests before parsing
  • Using a reverse proxy (such as NGINX) to enforce maximum request body sizes

Credited to Aarondoran.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology