CVE-2026-12590 Details
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.
A denial-of-service vulnerability exists in body-parser versions prior to 1.20.6 (1.x line) and 2.3.0 (2.x line). When the parser is set with an invalid limit option value, such as an unparseable string or NaN, the bytes.parse function returns null, causing the request body size check to be skipped without any notification. This oversight allows applications that depend on the limit to control request body size to accept excessively large payloads, resulting in increased memory and CPU consumption, and potential denial-of-service conditions. The vulnerability affects applications that provide a programmatically computed or user-configurable value for the limit option without prior validation.
This vulnerability is fixed in body-parser versions 1.20.6 and 2.3.0. After applying the update, invalid limit values will trigger a clear error during parser construction, rather than silently disabling the size enforcement. It is recommended to validate the limit value before passing it to body-parser, such as by using bytes.parse() to check for null or non-finite numbers.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jul 9, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://cna.openjsf.org/security-advisories.html | openjs | Vendor Advisory |
| https://github.com/expressjs/body-parser/security/advisories/GHSA-v422-hmwv-36x6 | openjs | MitigationPatchVendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-770 | Allocation of Resources Without Limits or Throttling | openjs |
Affected Products
| Product | Versions |
|---|---|
| openjsf body-parser | < 1.20.6 >= 2.0.0, < 2.3.0 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 10, 2026 | Initial Analysis | [email protected] |
| Jul 9, 2026 | CVE Modified | CISA-ADP |
| Jul 9, 2026 | New CVE Received | openjs |