CVE-2026-67318

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.6% (47th 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
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 5.3Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

axios versions >=1.13.0 (Node.js HTTP adapter) fail to enforce the configured maxBodyLength limit on streamed request bodies when requests are sent with httpVersion: 2. Because Node's HTTP/2 request API does not honor the maxBodyLength option and axios's byte-counting stream wrapper is gated on maxRedirects === 0, an attacker who controls a stream passed to axios can cause the application to transmit outbound data exceeding the configured finite maxBodyLength. Impact is limited to resource consumption and policy bypass (excess egress, upstream quota consumption, limited availability); it does not enable code execution, credential disclosure, or request-destination control. Calls using the default maxBodyLength: -1 and browser adapters are not affected.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
55
EG Risk 55/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
Severity53% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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.13.0 before 1.18.0 maxBodyLength Bypass via HTTP/2 | Advisories | VulnCheck

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

HTTP/2 streamed uploads bypass `maxBodyLength` · Advisory · axios/axios · GitHub

https://github.com/axios/axios/security/advisories/GHSA-mwf2-3pr3-8698

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

(2 across 2 ecosystems)
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 14× in last 7d / 73× 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 181 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-67318?
CVE-2026-67318 is a medium vulnerability published on August 1, 2026. axios versions >=1.13.0 (Node.js HTTP adapter) fail to enforce the configured maxBodyLength limit on streamed request bodies when requests are sent with httpVersion: 2. Because Node's HTTP/2 request API does not honor the maxBodyLength option and axios's byte-counting stream wrapper is gated on…
When was CVE-2026-67318 disclosed?
CVE-2026-67318 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-67318 actively exploited?
CVE-2026-67318 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67318?
CVE-2026-67318 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-67318?
A fix for CVE-2026-67318 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-67318 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-67318

Explore →

Is Your Infrastructure Affected by CVE-2026-67318?

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