CVE-2026-67317

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.4%, top 71% 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 1.7.0 before 1.18.0 fail to enforce maxBodyLength for WHATWG ReadableStream request bodies in the fetch adapter when Content-Length cannot be determined. Attackers can supply unknown-length stream data to bypass upload size limits and cause uncontrolled network egress or resource exhaustion.

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
29%
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 1.7.0 before 1.18.0 maxBodyLength Bypass via ReadableStream | Advisories | VulnCheck

https://www.vulncheck.com/advisories/axios-before-maxbodylength-bypass-via-readablestream
github Patch Available🟡 PoC Available

Fetch adapter `ReadableStream` uploads bypass `maxBodyLength` · Advisory · axios/axios · GitHub

https://github.com/axios/axios/security/advisories/GHSA-jqh4-m9w3-8hp9

Vendor Advisories for CVE-2026-67317(3)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatgrafana13-1-main-13.1.1-0.5.2.hum12026-08-05redhat
redhatgrafana13-1-main-13.1.1-0.5.hum12026-08-03redhat

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 23× in last 7d / 50× 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 01:30 UTCEPSS rescore
  2. 2026-08-14 19:03 UTCEG score recompute
  3. 2026-08-14 19:03 UTCVendor advisory
  4. 2026-08-14 19:03 UTCGHSA enrichment
  5. 2026-08-13 22:00 UTCEPSS rescore
  6. 2026-08-13 16:41 UTCVendor advisory
  7. 2026-08-13 16:41 UTCGHSA enrichment
  8. 2026-08-12 14:12 UTCEG score recompute
  9. 2026-08-12 14:12 UTCVendor advisory
  10. 2026-08-12 14:12 UTCGHSA enrichment
  11. 2026-08-12 13:51 UTCEPSS rescore
  12. 2026-08-11 11:50 UTCEG score recompute
  13. 2026-08-11 11:50 UTCVendor advisory
  14. 2026-08-11 11:50 UTCGHSA enrichment
  15. 2026-08-11 00:00 UTCEPSS rescore
  16. 2026-08-10 09:28 UTCEG score recompute
  17. 2026-08-10 09:28 UTCVendor advisory
  18. 2026-08-10 09:28 UTCGHSA enrichment
  19. 2026-08-09 13:47 UTCEPSS rescore
  20. 2026-08-09 07:07 UTCEG score recompute
  21. 2026-08-09 07:07 UTCVendor advisory
  22. 2026-08-09 07:07 UTCGHSA enrichment
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-08 04:45 UTCEG score recompute
  25. 2026-08-08 04:45 UTCVendor advisory
Show 25 more
  1. 2026-08-08 04:45 UTCGHSA enrichment
  2. 2026-08-07 02:24 UTCEG score recompute
  3. 2026-08-07 02:24 UTCVendor advisory
  4. 2026-08-07 02:24 UTCGHSA enrichment
  5. 2026-08-06 13:47 UTCEPSS rescore
  6. 2026-08-06 00:03 UTCEG score recompute
  7. 2026-08-06 00:03 UTCVendor advisory
  8. 2026-08-06 00:02 UTCGHSA enrichment
  9. 2026-08-05 19:17 UTCEPSS rescore
  10. 2026-08-05 19:17 UTCEPSS rescore
  11. 2026-08-04 21:41 UTCEG score recompute
  12. 2026-08-04 21:40 UTCGHSA enrichment
  13. 2026-08-04 15:10 UTCEPSS rescore
  14. 2026-08-04 10:39 UTCEPSS rescore
  15. 2026-08-03 19:19 UTCEG score recompute
  16. 2026-08-03 19:19 UTCGHSA enrichment
  17. 2026-08-03 19:05 UTCEG score recompute
  18. 2026-08-03 19:05 UTCGHSA enrichment
  19. 2026-08-03 18:05 UTCEG score recompute
  20. 2026-08-03 18:05 UTCGHSA enrichment
  21. 2026-08-03 10:36 UTCEPSS rescore
  22. 2026-08-02 15:41 UTCGHSA enrichment
  23. 2026-08-01 13:19 UTCEG score recompute
  24. 2026-08-01 12:44 UTCEG score recompute
  25. 2026-08-01 12:42 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-67317?
CVE-2026-67317 is a medium vulnerability published on August 1, 2026. axios versions 1.7.0 before 1.18.0 fail to enforce maxBodyLength for WHATWG ReadableStream request bodies in the fetch adapter when Content-Length cannot be determined. Attackers can supply unknown-length stream data to bypass upload size limits and cause uncontrolled network egress or resource…
When was CVE-2026-67317 disclosed?
CVE-2026-67317 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-67317 actively exploited?
CVE-2026-67317 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 71.1% of all scored CVEs.
What is the CVSS score of CVE-2026-67317?
CVE-2026-67317 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-67317?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67317, 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-67317

Explore →

Is Your Infrastructure Affected by CVE-2026-67317?

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

Start Free Scan →Browse All CVEs