CVE-2025-13466: body-parser · Uncontrolled Resource Consumption
Affects body-parserSource GCVE Database
Public exploit available · CVSS 5.5 Medium · fixed in 2.2.1 : patch body-parser as a priority.
Data as of 17 Nov 2026, 01:39 UTC
Thin evidence
One scorer or none| CNA (openjs) | CVSS 4.0 | 5.5 |
|---|
- Patch
- Available – fixed in 2.2.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L/E:P/AU:YExploitation evidence
Disclosed: evidence found.
CVE published 24 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| body-parser body-parser | Affected
| Fixed in– |
AI-suggested
Upgrade to body-parser version 2.2.1 or later, where this vulnerability has been fixed. No other mitigation or workaround is indicated.
Description
body-parser version 2.2.0 has a denial of service vulnerability due to inefficient processing of URL-encoded bodies with very large numbers of parameters. An attacker can exploit this by sending payloads with thousands of parameters within the default 100KB request size limit, causing high CPU and memory usage that may slow down or partially disrupt the service. This issue is fixed in version 2.2.1.