CVE-2026-67320

HIGHPre-NVD 8.38.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% 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 week
8.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.3Exploit: None knownExposed: 0

A fix is available — apply it.

axios in a Node.js deployment using the HTTP adapter can route requests through an attacker-controlled proxy. axios hardens merged request configuration by creating a null-prototype object, but request interceptors run after the merge; a common immutable interceptor pattern such as {...config} or Object.assign({}, config) converts the hardened config back into a regular object. axios then dispatches that object without re-hardening it, and the Node HTTP adapter reads config.proxy through the prototype chain. If an attacker can pollute Object.prototype.proxy, affected requests can be routed through an attacker-controlled proxy. For plaintext HTTP requests, the proxy can observe Authorization headers, Basic auth from config.auth, method, absolute URL, Host, and request body, and can return its own response. This does not establish browser impact or HTTPS header/body disclosure under normal TLS validation. Affected versions are >=0.31.1 (fixed in 0.33.0) and >=1.15.2 (fixed in 1.18.0).

CVSS v3
8.3
EG Score
8.3(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity83% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

August 1, 2026

Last Modified

August 3, 2026

Advisory Details (3)

Auto-updated Aug 1, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
generic

axios before 0.33.0 Prototype Pollution via Node HTTP adapter | Advisories | VulnCheck

https://www.vulncheck.com/advisories/axios-before-prototype-pollution-via-node-http-adapter
github_commit Patch Available

commit df53d7dd99b2 (axios/axios)

Patch available: axios/axios v1.16.0 (contains commit df53d7dd99b2)

https://github.com/axios/axios/commit/df53d7dd99b202fb194217abd127ae6a630e70dc
github Patch Available🟡 PoC Available

Axios Node HTTP adapter can use an inherited proxy after interceptor config cloning · Advisory · axios/axios · GitHub

https://github.com/axios/axios/security/advisories/GHSA-gcfj-64vw-6mp9

Vendor Advisories for CVE-2026-67320(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatjaeger-main-2.20.0-0.8.hum12026-07-30redhat
redhatgrafana13-1-main-13.1.1-0.3.hum12026-07-29redhat
redhatgrafana12-4-main-12.4.6-0.2.hum12026-07-28redhat

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 43× in last 7d / 81× 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 10:57 UTCEG score recompute
  2. 2026-08-15 10:57 UTCVendor advisory
  3. 2026-08-15 10:57 UTCGHSA enrichment
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-14 23:42 UTCVendor advisory
  6. 2026-08-14 23:42 UTCGHSA enrichment
  7. 2026-08-14 12:28 UTCVendor advisory
  8. 2026-08-14 12:28 UTCGHSA enrichment
  9. 2026-08-14 01:13 UTCEG score recompute
  10. 2026-08-14 01:13 UTCVendor advisory
  11. 2026-08-14 01:13 UTCGHSA enrichment
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-13 13:58 UTCVendor advisory
  14. 2026-08-13 13:58 UTCGHSA enrichment
  15. 2026-08-13 02:43 UTCVendor advisory
  16. 2026-08-13 02:43 UTCGHSA enrichment
  17. 2026-08-12 15:29 UTCEG score recompute
  18. 2026-08-12 15:29 UTCVendor advisory
  19. 2026-08-12 15:29 UTCGHSA enrichment
  20. 2026-08-12 13:51 UTCEPSS rescore
  21. 2026-08-12 04:07 UTCVendor advisory
  22. 2026-08-12 04:07 UTCGHSA enrichment
  23. 2026-08-11 16:52 UTCEG score recompute
  24. 2026-08-11 16:52 UTCVendor advisory
  25. 2026-08-11 16:52 UTCGHSA enrichment
Show 56 more
  1. 2026-08-11 05:38 UTCEG score recompute
  2. 2026-08-11 05:38 UTCVendor advisory
  3. 2026-08-11 05:38 UTCGHSA enrichment
  4. 2026-08-11 00:00 UTCEPSS rescore
  5. 2026-08-10 18:23 UTCVendor advisory
  6. 2026-08-10 18:23 UTCGHSA enrichment
  7. 2026-08-10 07:08 UTCVendor advisory
  8. 2026-08-10 07:08 UTCGHSA enrichment
  9. 2026-08-09 19:54 UTCEG score recompute
  10. 2026-08-09 19:54 UTCVendor advisory
  11. 2026-08-09 19:54 UTCGHSA enrichment
  12. 2026-08-09 13:47 UTCEPSS rescore
  13. 2026-08-09 08:39 UTCVendor advisory
  14. 2026-08-09 08:39 UTCGHSA enrichment
  15. 2026-08-08 21:25 UTCEG score recompute
  16. 2026-08-08 21:25 UTCVendor advisory
  17. 2026-08-08 21:25 UTCGHSA enrichment
  18. 2026-08-08 16:37 UTCEPSS rescore
  19. 2026-08-08 10:10 UTCVendor advisory
  20. 2026-08-08 10:10 UTCGHSA enrichment
  21. 2026-08-07 22:55 UTCEG score recompute
  22. 2026-08-07 22:55 UTCVendor advisory
  23. 2026-08-07 22:55 UTCGHSA enrichment
  24. 2026-08-07 11:41 UTCVendor advisory
  25. 2026-08-07 11:40 UTCGHSA enrichment
  26. 2026-08-07 00:24 UTCEG score recompute
  27. 2026-08-07 00:24 UTCVendor advisory
  28. 2026-08-07 00:24 UTCGHSA enrichment
  29. 2026-08-06 13:47 UTCEPSS rescore
  30. 2026-08-06 13:09 UTCVendor advisory
  31. 2026-08-06 13:09 UTCGHSA enrichment
  32. 2026-08-06 01:54 UTCEG score recompute
  33. 2026-08-06 01:54 UTCVendor advisory
  34. 2026-08-06 01:54 UTCGHSA enrichment
  35. 2026-08-05 19:17 UTCEPSS rescore
  36. 2026-08-05 19:17 UTCEPSS rescore
  37. 2026-08-05 14:39 UTCVendor advisory
  38. 2026-08-05 14:39 UTCGHSA enrichment
  39. 2026-08-05 03:24 UTCGHSA enrichment
  40. 2026-08-04 16:09 UTCEG score recompute
  41. 2026-08-04 16:09 UTCGHSA enrichment
  42. 2026-08-04 15:10 UTCEPSS rescore
  43. 2026-08-04 10:39 UTCEPSS rescore
  44. 2026-08-04 04:55 UTCGHSA enrichment
  45. 2026-08-03 17:40 UTCEG score recompute
  46. 2026-08-03 17:40 UTCGHSA enrichment
  47. 2026-08-03 16:19 UTCEG score recompute
  48. 2026-08-03 16:19 UTCGHSA enrichment
  49. 2026-08-03 10:36 UTCEPSS rescore
  50. 2026-08-03 10:24 UTCGHSA enrichment
  51. 2026-08-02 23:04 UTCGHSA enrichment
  52. 2026-08-02 11:49 UTCGHSA enrichment
  53. 2026-08-02 00:34 UTCGHSA enrichment
  54. 2026-08-01 13:19 UTCEG score recompute
  55. 2026-08-01 12:44 UTCEG score recompute
  56. 2026-08-01 12:42 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-67320?
CVE-2026-67320 is a high vulnerability published on August 1, 2026. axios in a Node.js deployment using the HTTP adapter can route requests through an attacker-controlled proxy. axios hardens merged request configuration by creating a null-prototype object, but request interceptors run after the merge; a common immutable interceptor pattern such as {...config} or…
When was CVE-2026-67320 disclosed?
CVE-2026-67320 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-67320 actively exploited?
CVE-2026-67320 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 77.1% of all scored CVEs.
What is the CVSS score of CVE-2026-67320?
CVE-2026-67320 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2026-67320?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67320, 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-67320

Explore →

Is Your Infrastructure Affected by CVE-2026-67320?

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

Start Free Scan →Browse All CVEs