CVE-2026-67312

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 73% 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, secondary
Trending — 4 sources updated this weekElevated
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.3Exploit: 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
6.3
EG Score
6.3(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity63% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

August 1, 2026

Last Modified

August 3, 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(4)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
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 (20 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-axios1.11.0+dfsg-1 ... 1.8.4+dfsg-1 (10 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 25× in last 7d / 53× 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.

  1. 2026-08-15 11:02 UTCEG score recompute
  2. 2026-08-15 11:02 UTCVendor advisory
  3. 2026-08-15 11:02 UTCGHSA enrichment
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-14 11:43 UTCEG score recompute
  6. 2026-08-14 11:43 UTCVendor advisory
  7. 2026-08-14 11:43 UTCGHSA enrichment
  8. 2026-08-13 22:00 UTCEPSS rescore
  9. 2026-08-13 12:24 UTCEG score recompute
  10. 2026-08-13 12:24 UTCVendor advisory
  11. 2026-08-13 12:24 UTCGHSA enrichment
  12. 2026-08-12 13:51 UTCEPSS rescore
  13. 2026-08-12 13:06 UTCVendor advisory
  14. 2026-08-12 13:06 UTCGHSA enrichment
  15. 2026-08-11 13:47 UTCEG score recompute
  16. 2026-08-11 13:47 UTCVendor advisory
  17. 2026-08-11 13:47 UTCGHSA enrichment
  18. 2026-08-11 00:00 UTCEPSS rescore
  19. 2026-08-10 14:28 UTCVendor advisory
  20. 2026-08-10 14:28 UTCGHSA enrichment
  21. 2026-08-09 15:09 UTCEG score recompute
  22. 2026-08-09 15:09 UTCVendor advisory
  23. 2026-08-09 15:09 UTCGHSA enrichment
  24. 2026-08-09 13:47 UTCEPSS rescore
  25. 2026-08-08 16:37 UTCEPSS rescore
Show 28 more
  1. 2026-08-08 15:51 UTCVendor advisory
  2. 2026-08-08 15:51 UTCGHSA enrichment
  3. 2026-08-07 16:32 UTCEG score recompute
  4. 2026-08-07 16:32 UTCVendor advisory
  5. 2026-08-07 16:32 UTCGHSA enrichment
  6. 2026-08-06 17:14 UTCEG score recompute
  7. 2026-08-06 17:14 UTCVendor advisory
  8. 2026-08-06 17:14 UTCGHSA enrichment
  9. 2026-08-06 13:47 UTCEPSS rescore
  10. 2026-08-05 19:17 UTCEPSS rescore
  11. 2026-08-05 19:17 UTCEPSS rescore
  12. 2026-08-05 17:55 UTCVendor advisory
  13. 2026-08-05 17:55 UTCGHSA enrichment
  14. 2026-08-04 18:37 UTCEG score recompute
  15. 2026-08-04 18:37 UTCGHSA enrichment
  16. 2026-08-04 15:10 UTCEPSS rescore
  17. 2026-08-04 10:39 UTCEPSS rescore
  18. 2026-08-03 19:19 UTCEG score recompute
  19. 2026-08-03 19:19 UTCGHSA enrichment
  20. 2026-08-03 19:05 UTCEG score recompute
  21. 2026-08-03 19:05 UTCGHSA enrichment
  22. 2026-08-03 11:56 UTCEG score recompute
  23. 2026-08-03 11:56 UTCGHSA enrichment
  24. 2026-08-03 10:36 UTCEPSS rescore
  25. 2026-08-02 12:37 UTCGHSA enrichment
  26. 2026-08-01 13:18 UTCEG score recompute
  27. 2026-08-01 12:43 UTCEG score recompute
  28. 2026-08-01 12:42 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-67312?
CVE-2026-67312 is a medium 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 August 3, 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 73.3% of all scored CVEs.
What is the CVSS score of CVE-2026-67312?
CVE-2026-67312 has a CVSS v3 base score of 6.3 (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