Advisory

GHSA-v422-hmwv-36x6

Also known as: CVE-2026-12590

Summary

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

Details

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

Severity

Low Basis: The source's own band: LOW

Dates

Published
2026-07-20 23:23 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

body-parser

npm · All systems

Affected

  • introduced 0, fixed 1.20.6 (semver)

Fixed versions

1.20.6

Fix

body-parser

npm · All systems

Affected

  • introduced 2.0.0, fixed 2.3.0 (semver)

Fixed versions

2.3.0

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences