CVE-2026-12590

MEDIUMNVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.9
EG Score
5.9(medium)
EG Risk
27(Track)
EG Risk 27/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity59% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

July 9, 2026

Last Modified

July 10, 2026

Advisory Details (2)

Auto-updated Jul 10, 2026
Patch available. Sources: github.
github Patch Available

body-parser vulnerable to denial of service when invalid limit value silently disables size enforcement · Advisory · expressjs/body-parser · GitHub

https://github.com/expressjs/body-parser/security/advisories/GHSA-v422-hmwv-36x6
generic

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html

Vendor Advisories for CVE-2026-12590(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
node-body-parser1.19.0-2 ... 2.3.0+~1.19.6-1 (18 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-body-parser1.20.1+~1.19.2-1 ... 2.3.0+~1.19.6-1 (11 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-body-parser1.20.3+~1.19.5-3 ... 2.3.0+~1.19.6-1 (7 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-body-parser1.20.3+~1.19.5-3 ... 2.2.2+~1.19.6-1 (6 versions)2.3.0+~1.19.6-1—
npm(1)
PackageVulnerable rangeFixed inDependents
body-parser—2.3.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 103 total refreshes for this CVE.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-18 05:37 UTCEG score recompute
  3. 2026-09-16 05:14 UTCEPSS rescore
  4. 2026-09-14 06:22 UTCEG score recompute
  5. 2026-09-13 16:46 UTCEPSS rescore
  6. 2026-09-13 08:20 UTCEG score recompute
  7. 2026-09-12 15:00 UTCEPSS rescore
  8. 2026-09-12 03:25 UTCEG score recompute
  9. 2026-09-11 14:52 UTCEPSS rescore
  10. 2026-09-11 09:36 UTCEPSS rescore
  11. 2026-09-10 09:34 UTCEPSS rescore
  12. 2026-09-08 22:00 UTCEPSS rescore
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-05 22:36 UTCEG score recompute
  16. 2026-09-04 05:06 UTCEPSS rescore
  17. 2026-09-02 14:11 UTCEPSS rescore
  18. 2026-09-01 13:53 UTCEPSS rescore
  19. 2026-09-01 04:39 UTCEPSS rescore
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 06:57 UTCEG score recompute
  22. 2026-08-30 01:21 UTCEPSS rescore
  23. 2026-08-28 21:40 UTCEPSS rescore
  24. 2026-08-27 23:59 UTCEG score recompute
  25. 2026-08-27 14:24 UTCEPSS rescore
Show 75 more
  1. 2026-08-27 01:57 UTCEG score recompute
  2. 2026-08-26 03:55 UTCEG score recompute
  3. 2026-08-25 13:48 UTCEPSS rescore
  4. 2026-08-24 20:21 UTCEG score recompute
  5. 2026-08-23 18:03 UTCEG score recompute
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-22 20:01 UTCEG score recompute
  8. 2026-08-21 23:48 UTCEPSS rescore
  9. 2026-08-20 23:52 UTCEG score recompute
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-20 01:50 UTCEG score recompute
  12. 2026-08-19 17:03 UTCEPSS rescore
  13. 2026-08-18 20:43 UTCEG score recompute
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-17 14:19 UTCEG score recompute
  16. 2026-08-16 16:16 UTCEG score recompute
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 18:14 UTCEG score recompute
  20. 2026-08-15 01:30 UTCEPSS rescore
  21. 2026-08-13 22:09 UTCEG score recompute
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-13 00:07 UTCEG score recompute
  24. 2026-08-12 13:50 UTCEPSS rescore
  25. 2026-08-12 02:05 UTCEG score recompute
  26. 2026-08-11 13:42 UTCEPSS rescore
  27. 2026-08-11 04:03 UTCEG score recompute
  28. 2026-08-10 23:59 UTCEPSS rescore
  29. 2026-08-10 06:00 UTCEG score recompute
  30. 2026-08-09 13:46 UTCEPSS rescore
  31. 2026-08-09 07:58 UTCEG score recompute
  32. 2026-08-08 16:37 UTCEPSS rescore
  33. 2026-08-08 09:56 UTCEG score recompute
  34. 2026-08-06 13:52 UTCEG score recompute
  35. 2026-08-06 13:46 UTCEPSS rescore
  36. 2026-08-05 19:17 UTCEPSS rescore
  37. 2026-08-04 16:50 UTCEG score recompute
  38. 2026-08-04 15:09 UTCEPSS rescore
  39. 2026-08-04 10:38 UTCEPSS rescore
  40. 2026-08-03 18:48 UTCEG score recompute
  41. 2026-08-03 10:35 UTCEPSS rescore
  42. 2026-08-02 20:46 UTCEG score recompute
  43. 2026-08-02 02:26 UTCEPSS rescore
  44. 2026-08-01 22:44 UTCEG score recompute
  45. 2026-08-01 04:15 UTCEPSS rescore
  46. 2026-07-31 02:38 UTCEG score recompute
  47. 2026-07-30 16:27 UTCEPSS rescore
  48. 2026-07-30 04:32 UTCEG score recompute
  49. 2026-07-30 01:30 UTCEPSS rescore
  50. 2026-07-29 06:29 UTCEG score recompute
  51. 2026-07-28 15:36 UTCEPSS rescore
  52. 2026-07-28 08:26 UTCEG score recompute
  53. 2026-07-27 14:13 UTCEPSS rescore
  54. 2026-07-27 10:23 UTCEG score recompute
  55. 2026-07-26 14:54 UTCEPSS rescore
  56. 2026-07-26 14:54 UTCEPSS rescore
  57. 2026-07-26 12:21 UTCEG score recompute
  58. 2026-07-25 14:17 UTCEPSS rescore
  59. 2026-07-24 14:17 UTCEPSS rescore
  60. 2026-07-23 14:18 UTCEPSS rescore
  61. 2026-07-23 03:05 UTCEG score recompute
  62. 2026-07-22 14:08 UTCEPSS rescore
  63. 2026-07-21 15:24 UTCEPSS rescore
  64. 2026-07-20 17:08 UTCEPSS rescore
  65. 2026-07-19 14:30 UTCEPSS rescore
  66. 2026-07-19 02:28 UTCEPSS rescore
  67. 2026-07-18 10:04 UTCEPSS rescore
  68. 2026-07-16 17:02 UTCEPSS rescore
  69. 2026-07-15 16:57 UTCEPSS rescore
  70. 2026-07-15 02:00 UTCEPSS rescore
  71. 2026-07-13 22:30 UTCEPSS rescore
  72. 2026-07-13 06:12 UTCEPSS rescore
  73. 2026-07-12 06:41 UTCEG score recompute▲ 2.20
  74. 2026-07-12 05:46 UTCEPSS rescore
  75. 2026-07-11 08:27 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-12590?
CVE-2026-12590 is a medium vulnerability published on July 9, 2026. 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…
When was CVE-2026-12590 disclosed?
CVE-2026-12590 was first published in the National Vulnerability Database on July 9, 2026, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12590 actively exploited?
CVE-2026-12590 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.8% of all scored CVEs.
What is the CVSS score of CVE-2026-12590?
CVE-2026-12590 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-12590?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12590, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-12590

Explore →

Is Your Infrastructure Affected by CVE-2026-12590?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs