Vulnerability · CVE-2025-13466
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.
Published Nov 24, 2025 · catalog updated Nov 24, 2025 · body-parser 2.2.0 is vulnerable
Last checked Nov 6, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2025-13466. EPSS is 0.39%. Act only if a listed version of body-parser 2.2.0 is vulnerable is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (body-parser 2.2.0 is vulnerable).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Medium5.5
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.39%
- Remediation
- Advisory link
- Affected products
- vendor body-parser body-parser 2.2.0
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. This issue is addressed in version 2.2.1.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor body-parser body-parser 2.2.02.2.0
How to fix CVE-2025-13466
No stored fix
No vendor fix text is stored. Use the linked advisory before you change production.
Version check
Seen in 2.2.0
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2025-13466. EPSS is 0.39%. Act only if a listed version of body-parser 2.2.0 is vulnerable is installed.
Which versions are affected?
Compare what you have installed with body-parser body-parser 2.2.0 2.2.0. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.39%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Nov 24, 2025 · EUVD
Detected
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. This issue is address
Nov 24, 2025 · EUVD
Updated
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. This issue is address
Sources
- CVE.orgVulnerability recordCVE-2025-13466
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2025-13466
30-day exploitation probability 0.39%
first.org - EUVDVulnerability recordEUVD-2025-198982
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 mem
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSNov 6, 2026
- CVE.orgOct 28, 2026
- EUVDOct 28, 2026