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

CVE-2026-12590: body-parser vulnerable to denial of service when invalid limit value silently disables size enforcement

lowCVSS 3.1 3.7GHSA-v422-hmwv-36x6

Impact When body-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.

Published Jul 20, 2026

Affected packages

body-parser

Ecosystem
npm
Affected
< 1.20.6
Fixed in
1.20.6
Check
npm ls body-parser

body-parser

Ecosystem
npm
Affected
>= 2.0.0, < 2.3.0
Fixed in
2.3.0
Check
npm ls body-parser

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

When body-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.

This issue affects applications that pass a programmatically computed or user-configurable value to the limit option without validating it first.

Patches

This issue is fixed in [email protected] and [email protected] via #698. After the fix, invalid limit values throw a clear error at parser construction time instead of silently disabling enforcement. null and undefined continue to fall back to the default limit (100kb).

Workarounds

Validate limit before passing it to body-parser. For example, parse the value with `bytes.parse()` at startup and reject any configuration where it returns null or a non-finite number.

References

Credited to Phillip9587, efekrskl, UlisesGascon, bjohansebas.

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

More npm vulnerabilities

All npm entries