CVE-2026-67312

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 63% 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
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

axios versions from 0.28.0 before 0.33.0 and from 1.0.0 before 1.18.0 contain uncontrolled recursion in formDataToJSON (exposed as axios.formToJSON() and used internally when serializing FormData with Content-Type: application/json). When an application passes attacker-controlled FormData field names, a field name with thousands of nested bracket-delimited segments causes unbounded recursion in buildPath(), exhausting the JavaScript call stack (RangeError: Maximum call stack size exceeded) and causing denial of service for that request, or process termination in applications without appropriate error handling.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
50(Track)
EG Risk 50/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
Severity75% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

August 1, 2026

Last Modified

September 1, 2026

Advisory Details (2)

Auto-updated Aug 1, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

axios 0.28.0 before 0.33.0 Denial of Service via formToJSON | Advisories | VulnCheck

https://www.vulncheck.com/advisories/axios-before-denial-of-service-via-formtojson
github Patch Available🟡 PoC Available

Deep formToJSON Key Recursion Can Cause Denial of Service · Advisory · axios/axios · GitHub

https://github.com/axios/axios/security/advisories/GHSA-pmv8-rq9r-6j72

Vendor Advisories for CVE-2026-67312(5)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhdh/rhdh-hub-rhel9:17882860492026-09-02redhat
redhatjaeger-main-2.20.0-0.8.hum12026-07-30redhat
redhatgrafana13-1-main-13.1.1-0.3.hum12026-07-29redhat
redhatgrafana12-4-main-12.4.6-0.2.hum12026-07-28redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
node-axios0.21.1+dfsg-1 ... 1.8.4+dfsg-1 (40 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-axios1.11.0+dfsg-1 ... 1.8.4+dfsg-1 (22 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-axios1.11.0+dfsg-1 ... 1.8.4+dfsg-1 (12 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-axios1.11.0+dfsg-1 ... 1.8.4+dfsg-1 (9 versions)1.18.0-1—
npm(1)
PackageVulnerable rangeFixed inDependents
axios—1.18.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 99× 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 168 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-67312?
CVE-2026-67312 is a high vulnerability published on August 1, 2026. axios versions from 0.28.0 before 0.33.0 and from 1.0.0 before 1.18.0 contain uncontrolled recursion in formDataToJSON (exposed as axios.formToJSON() and used internally when serializing FormData with Content-Type: application/json). When an application passes attacker-controlled FormData field…
When was CVE-2026-67312 disclosed?
CVE-2026-67312 was first published in the National Vulnerability Database on August 1, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67312 actively exploited?
CVE-2026-67312 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 62.9% of all scored CVEs.
What is the CVSS score of CVE-2026-67312?
CVE-2026-67312 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-67312?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67312, 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-67312

Explore →

Is Your Infrastructure Affected by CVE-2026-67312?

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

Start Free Scan →Browse All CVEs