CVE-2026-12590: body-parser vulnerable to denial of service when invalid limit value silently disables size enforcement
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
- https://github.com/expressjs/body-parser/security/advisories/GHSA-v422-hmwv-36x6
- https://nvd.nist.gov/vuln/detail/CVE-2026-12590
- https://github.com/expressjs/body-parser/pull/698
- https://github.com/expressjs/body-parser/pull/741
- https://github.com/expressjs/body-parser/commit/2322e111cc321413ec2b7b76d01be533d3de9d7d
- https://github.com/expressjs/body-parser/commit/3492672eee593d5c158f239b6e9115498a5dbeac
- https://cna.openjsf.org/security-advisories.html
- https://github.com/expressjs/body-parser/releases/tag/1.20.6
- https://github.com/expressjs/body-parser/releases/tag/v2.3.0
- https://github.com/advisories/GHSA-v422-hmwv-36x6
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 entriesCVE-2026-111181
body-parser vulnerable to Denial of Service via trailing bytes after a compressed request body
high7.5Oct 23, 2026CVE-2025-13466
body-parser is vulnerable to denial of service when url encoding is used
medium5.3Nov 25, 2025CVE-2024-45590
body-parser vulnerable to denial of service when url encoding is enabled
high7.5Sep 10, 2024
