CVE-2026-67318

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.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
6.3
EG Score
6.3(medium)
EG Risk
59(Attend)
EG Risk 59/100SSVC: Attend

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%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
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.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

Vendor Advisories for CVE-2026-67318(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

(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 26× 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 01:30 UTCEPSS rescore
  2. 2026-08-14 20:38 UTCVendor advisory
  3. 2026-08-14 20:38 UTCGHSA enrichment
  4. 2026-08-13 22:36 UTCEG score recompute
  5. 2026-08-13 22:36 UTCVendor advisory
  6. 2026-08-13 22:36 UTCGHSA enrichment
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-13 00:34 UTCEG score recompute
  9. 2026-08-13 00:34 UTCVendor advisory
  10. 2026-08-13 00:34 UTCGHSA enrichment
  11. 2026-08-12 13:51 UTCEPSS rescore
  12. 2026-08-12 02:33 UTCEG score recompute
  13. 2026-08-12 02:33 UTCVendor advisory
  14. 2026-08-12 02:33 UTCGHSA enrichment
  15. 2026-08-11 04:32 UTCEG score recompute
  16. 2026-08-11 04:32 UTCVendor advisory
  17. 2026-08-11 04:32 UTCGHSA enrichment
  18. 2026-08-11 00:00 UTCEPSS rescore
  19. 2026-08-10 06:30 UTCEG score recompute
  20. 2026-08-10 06:30 UTCVendor advisory
  21. 2026-08-10 06:30 UTCGHSA enrichment
  22. 2026-08-09 13:47 UTCEPSS rescore
  23. 2026-08-09 08:29 UTCEG score recompute
  24. 2026-08-09 08:29 UTCVendor advisory
  25. 2026-08-09 08:29 UTCGHSA enrichment
Show 28 more
  1. 2026-08-08 16:37 UTCEPSS rescore
  2. 2026-08-08 10:28 UTCEG score recompute
  3. 2026-08-08 10:28 UTCVendor advisory
  4. 2026-08-08 10:28 UTCGHSA enrichment
  5. 2026-08-07 12:26 UTCVendor advisory
  6. 2026-08-07 12:26 UTCGHSA enrichment
  7. 2026-08-06 14:25 UTCEG score recompute
  8. 2026-08-06 14:25 UTCVendor advisory
  9. 2026-08-06 14:25 UTCGHSA enrichment
  10. 2026-08-06 13:47 UTCEPSS rescore
  11. 2026-08-05 19:17 UTCEPSS rescore
  12. 2026-08-05 19:17 UTCEPSS rescore
  13. 2026-08-05 16:23 UTCVendor advisory
  14. 2026-08-05 16:23 UTCGHSA enrichment
  15. 2026-08-04 18:22 UTCEG score recompute
  16. 2026-08-04 18:22 UTCGHSA enrichment
  17. 2026-08-04 15:10 UTCEPSS rescore
  18. 2026-08-04 10:39 UTCEPSS rescore
  19. 2026-08-03 20:20 UTCEG score recompute
  20. 2026-08-03 20:20 UTCGHSA enrichment
  21. 2026-08-03 20:14 UTCEG score recompute
  22. 2026-08-03 20:14 UTCGHSA enrichment
  23. 2026-08-03 10:36 UTCEPSS rescore
  24. 2026-08-03 09:25 UTCGHSA enrichment
  25. 2026-08-02 11:20 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-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 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-67318 actively exploited?
CVE-2026-67318 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.4% of all scored CVEs.
What is the CVSS score of CVE-2026-67318?
CVE-2026-67318 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-67318?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67318, 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-67318

Explore →

Is Your Infrastructure Affected by CVE-2026-67318?

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

Start Free Scan →Browse All CVEs