Alert IDs:
- 006fd1aa-fe5b-4256-b6ba-4a21c6841f12
- 2d4c6cd3-31dd-4ce3-b680-bb4ad4901356
Vulnerabilities in body-parser
Release: New release
Total Vulnerabilities: 2
Severity: MEDIUM (Score: 4.8)
Description:
Impact
body-parser 2.2.0 is vulnerable to denial of service due to inefficient handling of URL-encoded bodies with very large numbers of parameters. An attacker can send payloads containing thousands of parameters within the default 100KB request size limit, causing elevated CPU and memory usage. This can lead to service slowdown or partial outages under sustained malicious traffic.
Patches
This issue is addressed in version 2.2.1.
Reference: https://nvd.nist.gov/vuln/detail/CVE-2025-13466
Alert ID: 006fd1aa-fe5b-4256-b6ba-4a21c6841f12
Severity: LOW (Score: 3.6)
Description:
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 body-parser@2.3.0 and body-parser@1.20.6 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
Reference: https://nvd.nist.gov/vuln/detail/CVE-2026-12590
Alert ID: 2d4c6cd3-31dd-4ce3-b680-bb4ad4901356
Alert IDs:
Vulnerabilities in body-parser
Release: New release
Total Vulnerabilities: 2
1. CVE-2025-13466
Severity: MEDIUM (Score: 4.8)
Description:
Impact
body-parser 2.2.0 is vulnerable to denial of service due to inefficient handling of URL-encoded bodies with very large numbers of parameters. An attacker can send payloads containing thousands of parameters within the default 100KB request size limit, causing elevated CPU and memory usage. This can lead to service slowdown or partial outages under sustained malicious traffic.
Patches
This issue is addressed in version 2.2.1.
Reference: https://nvd.nist.gov/vuln/detail/CVE-2025-13466
Alert ID: 006fd1aa-fe5b-4256-b6ba-4a21c6841f12
2. CVE-2026-12590
Severity: LOW (Score: 3.6)
Description:
Impact
When body-parser is configured with an invalid
limitoption value, such as an unparseable string orNaN,bytes.parse()returnsnulland the request body size check is silently skipped. Applications that rely onlimitas 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
limitoption without validating it first.Patches
This issue is fixed in body-parser@2.3.0 and body-parser@1.20.6 via #698. After the fix, invalid
limitvalues throw a clear error at parser construction time instead of silently disabling enforcement.nullandundefinedcontinue to fall back to the default limit (100kb).Workarounds
Validate
limitbefore passing it to body-parser. For example, parse the value withbytes.parse()at startup and reject any configuration where it returnsnullor a non-finite number.References
Reference: https://nvd.nist.gov/vuln/detail/CVE-2026-12590
Alert ID: 2d4c6cd3-31dd-4ce3-b680-bb4ad4901356