Vulnerability Description
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.
CVSS Score
LOW
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Openjsf | Body-Parser | < 1.20.6 |
Related Weaknesses (CWE)
References
- https://cna.openjsf.org/security-advisories.htmlVendor Advisory
- https://github.com/expressjs/body-parser/security/advisories/GHSA-v422-hmwv-36x6MitigationPatchVendor Advisory
FAQ
What is CVE-2026-12590?
CVE-2026-12590 is a vulnerability with a CVSS score of 3.7 (LOW). 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 retu...
How severe is CVE-2026-12590?
CVE-2026-12590 has been rated LOW with a CVSS base score of 3.7/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-12590?
Check the references section above for vendor advisories and patch information. Affected products include: Openjsf Body-Parser.