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.4%, top 63% 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
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.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
5.3
EG Score
5.3(medium)
EG Risk
55(Attend)
EG Risk 55/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
Severity53% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
37%
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.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 16× in last 7d / 89× 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 160 total refreshes for this CVE.

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

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 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% probability of exploitation in the next 30 days, which ranks it in the top 63.3% of all 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?
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