CVE-2025-67731
Servify-express rate limit issue
Impact
### 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
Affected packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| npm | servify-express | <= 1.1 | 1.2 |
Affected products
| Vendor | Product | Affected versions |
|---|---|---|
| Servify-Express.Js | Servify Express | before 1.2 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- https://github.com/Aarondoran/servify-express/commit/8dff7f56504b356278d849734ef2050e5cd23b61
- https://github.com/Aarondoran/servify-express/releases/tag/V1.2
- https://github.com/Aarondoran/servify-express/security/advisories/GHSA-qgc4-8p88-4w7m
- https://github.com/advisories/GHSA-qgc4-8p88-4w7m
- https://github.com/Aarondoran/servify-express/commit/197d848e5450bf85b0dd19ef8c2aa4ba96192300
- https://nvd.nist.gov/vuln/detail/CVE-2025-67731