Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
3.7

body-parser may ignore size limits, causing DoS

published 10 days ago
Summary

Older versions of the body-parser library used in several hardened Docker images can fail to enforce request size limits if the limit setting is incorrect. This lets attackers send very large requests that can exhaust memory and CPU, potentially crashing the service. Update to the latest versions of the Docker images or ensure the limit value is a valid number before configuring body-parser.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
Ecosystem VendorProductAffected versions
Docker Hardened Images:Alpine:3.24 docker hardened images jupyterhub-k8s-singleuser-sample-fips All versions
Docker Hardened Images:Debian:13 docker hardened images datahub-ingestion All versions
Docker Hardened Images:Debian:13 docker hardened images jupyterhub-k8s-singleuser-sample-fips All versions
Docker Hardened Images:Debian:13 docker hardened images jupyterhub-k8s-singleuser-sample All versions
Original advisory text
Impact: In body-parser versions prior to 1.20.6 (1.x line) and 2.3.0 (2.x line), when the parser is configured with an…
Impact: In body-parser versions prior to 1.20.6 (1.x line) and 2.3.0 (2.x line), when the parser is configured with an invalid limit option value such as an unparseable string or NaN, bytes.parse returns null and the request body size check is silently skipped. Applications that rely on limit as their primary safeguard against oversized request bodies will accept arbitrarily large payloads, leading to excessive memory and CPU usage and denial of service. Patches: This issue is fixed in body-parser 1.20.6 and 2.3.0. After the fix, invalid limit values throw a clear error at parser construction time instead of silently disabling enforcement, while null and undefined continue to fall back to the default limit of 100kb. Workarounds: Validate the limit value before passing it to body-parser. For example, parse the value at startup and reject any configuration where the result is null or a non-finite number.
Fix within
Internet-facing 14 days
Internal 60 days
  • Not known to be exploited
  • Can be exploited automatically (estimated)
  • Gives an attacker partial control (estimated)
Severity
3.7 Low
Timeline
Published11 Nov 2026
Updated16 Nov 2026
First seen16 Nov 2026
Sources
Track software like this
Free during beta