body-parser is vulnerable to denial of service when url encoding is used
Published 25 Nov 2025 · Updated 10 Sept 2026
Affected package
- Affected
- >=2.2.0 <2.2.1
- Fixed in
- 2.2.1
npm install body-parser@2.2.1Details
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.
Is GHSA-wqch-xfxh-vrr4 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected body-parser, and gives you the command that fixes it.
References
- Linkgithub.com/expressjs/body-parser/security/advisories/GHSA-wqch-xfxh-vrr4
- Advisorynvd.nist.gov/vuln/detail/CVE-2025-13466
- Linkgithub.com/expressjs/body-parser/commit/b204886a6744b0b6d297cd0e849d75de836f3b63
- Packagegithub.com/expressjs/body-parser
- Linkgithub.com/expressjs/body-parser/releases/tag/v2.2.1
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.