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.
References
| Link | Resource |
|---|---|
| https://cna.openjsf.org/security-advisories.html | Vendor Advisory |
| https://github.com/expressjs/body-parser/security/advisories/GHSA-v422-hmwv-36x6 | Mitigation Patch Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
10 Jul 2026, 02:45
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://cna.openjsf.org/security-advisories.html - Vendor Advisory | |
| References | () https://github.com/expressjs/body-parser/security/advisories/GHSA-v422-hmwv-36x6 - Mitigation, Patch, Vendor Advisory | |
| First Time |
Openjsf body-parser
Openjsf |
|
| CPE | cpe:2.3:a:openjsf:body-parser:*:*:*:*:*:node.js:*:* |
09 Jul 2026, 11:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-07-09 11:16
Updated : 2026-07-10 02:45
NVD link : CVE-2026-12590
Mitre link : CVE-2026-12590
CVE.ORG link : CVE-2026-12590
JSON object : View
Products Affected
openjsf
- body-parser
CWE
CWE-770
Allocation of Resources Without Limits or Throttling