CVE-2026-67317

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 58% 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: 1%CVSS: 7.5Exploit: 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
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
1%
EPSS %ILE
42%
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 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 (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 21× in last 7d / 94× 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 163 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-67317?
CVE-2026-67317 is a high 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 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-67317 actively exploited?
CVE-2026-67317 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 58.2% of all scored CVEs.
What is the CVSS score of CVE-2026-67317?
CVE-2026-67317 has a CVSS v3 base score of 7.5 (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