CVE-2025-13466
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedbody-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencebody-parser 2.2.0 has inefficient algorithmic complexity when parsing URL-encoded form data containing very large numbers of parameters. An attacker can send thousands of parameters within the default 100KB size limit, causing the parser to consume excessive CPU and memory, leading to service degradation or partial outages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- Y
- User interaction
- None
- Scope
- X
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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate body-parser in your projectRun 'npm list body-parser' in your project directory, or inspect package.json for body-parser in dependenciesAffected if body-parser is listed in node_modules or package.json
-
Determine installed body-parser versionRun 'npm list body-parser' to see the installed version, or check the version field in node_modules/body-parser/package.jsonAffected if The installed version is exactly 2.2.0
-
Confirm URL-encoded form parsing is enabledSearch your application code for calls to body-parser's urlencoded() middleware, such as app.use(bodyParser.urlencoded(...)) or app.use(require('body-parser').urlencoded(...))Affected if URL-encoded parsing is enabled with default settings (no limit on parameter count)
-
Check request size limit configurationInspect the urlencoded() configuration options, specifically looking for the 'limit' parameterAffected if The limit is set to the default 100KB or is not explicitly configured, allowing large numbers of parameters within that size bound
Your environment is affected if body-parser version 2.2.0 is installed and URL-encoded form parsing is enabled without parameter count limits.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade body-parser to version 2.2.1. Additionally, consider implementing parameter count limits or request throttling at the application or reverse proxy level as a defense-in-depth measure.
body-parser version 2.2.1
- Check the current version of body-parser in your project by running: npm list body-parser
- Upgrade body-parser to version 2.2.1 or later by running: npm install [email protected]
- After upgrading, verify the installation: npm list body-parser
- If you use a package-lock.json or yarn.lock, ensure the lock file is updated and review changes in your dependency tree
- Test your application to confirm the upgrade does not break existing functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13466 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13466 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data