Vulnerability in body-parser (CVE-2026-12590)
Summary
Vulnerability in body-parser (CVE-2026-12590). Risk of unauthorized operations or information disclosure. Exploitable via limit. Mitigation: upgrade to 2.3.0 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-12590 has been found in body-parser.
Attackers can target a specific entry point like limit over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.7/10.
What to do: upgrade body-parser to 2.3.0 or later.
If unsure, ask your IT team or search "body-parser CVE-2026-12590" on the vendor's site.
CVE-2026-12590 (body-parser) — CWE-770 / CVSS v3 3.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: limit / NaN / null / undefined
Patched: 2.3.0 — apply immediately
Workaround: Validate limit before passing it to body-parser.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-770) exists in body-parser. Attackers reach the vulnerable code path via limit without authentication.
Check the vendor advisory for the affected versions of body-parser. Attack surface: limit / NaN / null / undefined.
Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.
Update to 2.3.0.
Workaround: Validate limit before passing it to body-parser.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'body-parser' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'body-parser' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
body-parserを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Validate `limit` before passing it to body-parser.パッチが適用されるまでの応急処置として、Validate
limitbefore passing it to body-parser. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade body-parser to 2.3.0ステージング環境で 2.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-12590 node-body-parser
- Ubuntu UBUNTU-CVE-2026-12590 node-body-parser
References
- advisory cna.openjsf.org
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com