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.6% (46th percentile of EPSS-scored CVEs). 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.6%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
50
EG Risk 50/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
46th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

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 16× in last 7d / 85× 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 186 total refreshes for this CVE.

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

Related CVEs(same product + 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 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 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-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?
A fix for CVE-2026-67317 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-67317 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs