← Back
CVE-2026-12590
low
CVSS 3.7
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**A vulnerability** (CWE-770) exists in body-parser. Attackers reach the vulnerable code path via ``limit`` without authentication.
📍 Affected scope
body-parser — . Attack surface: `limit` / `NaN` / `null` / `undefined`.
🔥 Severity
Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.3.0**.
🛡️ Workaround
Workaround: Validate `limit` before passing it to body-parser.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Validate `limit` before passing it to body-parser.パッチが適用されるまでの応急処置として、Validate `limit` before passing it to body-parser. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade body-parser to 2.3.0ステージング環境で 2.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
body-parser
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.3.0"}]}]
References
- web https://cna.openjsf.org/security-advisories.html
- web https://github.com/expressjs/body-parser/security/advisories/GHSA-v422-hmwv-36x6
- web https://nvd.nist.gov/vuln/detail/CVE-2026-12590
- web https://github.com/expressjs/body-parser/pull/698
- web https://github.com/expressjs/body-parser/pull/741
- web https://github.com/expressjs/body-parser/commit/2322e111cc321413ec2b7b76d01be533d3de9d7d
- web https://github.com/expressjs/body-parser/commit/3492672eee593d5c158f239b6e9115498a5dbeac
- web https://github.com/expressjs/body-parser/releases/tag/1.20.6
- web https://github.com/expressjs/body-parser/releases/tag/v2.3.0
- web https://github.com/advisories/GHSA-v422-hmwv-36x6