GHSA-qgc4-8p88-4w7mHigh

Servify-express rate limit issue

Published
December 11, 2025
Last Modified
December 12, 2025

🔗 CVE IDs covered (1)

📋 Description

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 products1

  • npm/servify-express:<= 1.1

🔗 References (6)