Alert IDs:
- 8887c3ff-4911-4b4c-bdf0-e53c5f5e438b
- c0ab3c18-6944-45ab-b06e-665875610234
Vulnerabilities in body-parser
Release: New release
Total Vulnerabilities: 2
Severity: LOW (Score: 3.6)
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.
Reference: https://nvd.nist.gov/vuln/detail/CVE-2026-12590
Alert ID: 8887c3ff-4911-4b4c-bdf0-e53c5f5e438b
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: c0ab3c18-6944-45ab-b06e-665875610234
Alert IDs:
Vulnerabilities in body-parser
Release: New release
Total Vulnerabilities: 2
1. CVE-2026-12590
Severity: LOW (Score: 3.6)
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.
Reference: https://nvd.nist.gov/vuln/detail/CVE-2026-12590
Alert ID: 8887c3ff-4911-4b4c-bdf0-e53c5f5e438b
2. 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: c0ab3c18-6944-45ab-b06e-665875610234