CVE-2026-67320

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 69% 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 week
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%CVSS: 7.5Exploit: 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
7.5
EG Score
7.5(medium)
EG Risk
34(Track)
EG Risk 34/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
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

August 1, 2026

Last Modified

September 1, 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(20)

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

Patch Availability(20)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatquay/quay-rhel8:17885943762026-09-10redhat
redhatquay/quay-rhel8:17885618412026-09-09redhat
redhatquay/quay-rhel8:17885955742026-09-08redhat
redhatrhoai/odh-mod-arch-model-registry-rhel9:17883121572026-09-08redhat
redhatansible-automation-platform/automation-portal:17887757482026-09-08redhat
redhatsatellite/iop-host-inventory-frontend-rhel9:17882609412026-09-03redhat
redhatsatellite/iop-host-inventory-frontend-rhel9:17883222432026-09-03redhat
redhatquay/quay-rhel8:17881917552026-09-03redhat
redhatcontainer-native-virtualization/kubevirt-console-plugin:17876510052026-08-31redhat
redhatrhacm2/console-rhel9:17873392482026-08-26redhat
redhatrhacm2/console-rhel9:17873392492026-08-26redhat
redhatrhacm2/console-rhel9:17876870622026-08-26redhat
redhatopenshift-service-mesh/kiali-rhel9:17870771082026-08-25redhat
redhatopenshift-service-mesh/kiali-rhel9:17870921982026-08-25redhat
redhatopenshift-service-mesh/kiali-rhel9:17871656832026-08-25redhat
redhatopenshift-service-mesh/kiali-rhel9:17870764952026-08-25redhat
redhatopenshift-service-mesh/kiali-rhel9:17870922552026-08-25redhat
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 20× in last 7d / 118× 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 228 total refreshes for this CVE.

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

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 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-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 69.2% of all scored CVEs.
What is the CVSS score of CVE-2026-67320?
CVE-2026-67320 has a CVSS v3 base score of 7.5 (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