CVE-2026-67320

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.5% (44th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-51847 (ENISA EUVD) · GHSA-68jp-44vc-2x5h (GitHub Security Advisories) · GHSA-gcfj-64vw-6mp9 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 1, 2026

Last Modified

September 1, 2026

Advisory Details (3)

Auto-updated Aug 1, 2026
Patch available. Sources: github, github_commit.
Web page

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 advisoryMentions a patch (unverified)

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(32)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-mod-arch-model-registry-rhel9:17918609182026-10-19redhat
redhatquay/quay-rhel9:17912655902026-10-12redhat
redhatquay/quay-rhel9:17906902982026-10-01redhat
redhatquay/quay-rhel8:17885938432026-09-22redhat
redhatquay/quay-rhel9:17895637532026-09-21redhat
redhatrhmtc/openshift-migration-ui-rhel8:17895463732026-09-17redhat
redhatsatellite/iop-advisor-frontend-rhel9:17896595652026-09-17redhat
redhatdevspaces/dashboard-rhel9:17891628842026-09-17redhat
redhatsatellite/iop-vulnerability-frontend-rhel9:17896609832026-09-17redhat
redhatsatellite/iop-vulnerability-frontend-rhel9:17896609692026-09-17redhat
redhatquay/quay-rhel8:17885943762026-09-10redhat
redhatquay/quay-rhel8:17885618412026-09-09redhat
redhatrhoai/odh-mod-arch-model-registry-rhel9:17883121572026-09-08redhat
redhatquay/quay-rhel8:17885955742026-09-08redhat
redhatansible-automation-platform/automation-portal:17887757482026-09-08redhat
redhatsatellite/iop-host-inventory-frontend-rhel9:17882609412026-09-03redhat
redhatquay/quay-rhel8:17881917552026-09-03redhat
redhatsatellite/iop-host-inventory-frontend-rhel9:17883222432026-09-03redhat
redhatcontainer-native-virtualization/kubevirt-console-plugin:17876510052026-08-31redhat
redhatrhacm2/console-rhel9:17873392492026-08-26redhat
redhatrhacm2/console-rhel9:17873392482026-08-26redhat
redhatrhacm2/console-rhel9:17876870622026-08-26redhat
redhatopenshift-service-mesh/kiali-rhel9:17870922552026-08-25redhat
redhatopenshift-service-mesh/kiali-rhel9:17871656832026-08-25redhat
redhatopenshift-service-mesh/kiali-rhel9:17870764952026-08-25redhat
redhatopenshift-service-mesh/kiali-rhel9:17870771082026-08-25redhat
redhatopenshift-service-mesh/kiali-rhel9:17870921982026-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
npmaxios @ 0.33.0 (fixes >= 0.31.1, < 0.33.0)—ghsa
npmaxios @ 1.18.0 (fixes >= 1.15.2, < 1.18.0)—ghsa

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 rangeFix by version rangeDependents
node-axios1.11.0+dfsg-1 ... 1.8.4+dfsg-1 (9 versions)
  • every version up to 1.18.0-1: fixed in 1.18.0-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
axios—
  • 0.31.1 up to 0.33.0: fixed in 0.33.0
  • 1.15.2 up to 1.18.0: fixed in 1.18.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(14)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 11× in last 7d / 52× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 315 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 215 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  2. 2026-11-01 07:40 UTCGHSA enrichmentGHSA-gcfj-64vw-6mp9 · GitHub severity HIGH
  3. 2026-11-01 07:40 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  5. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  6. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  7. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  8. 2026-10-28 06:31 UTCEG score recompute
  9. 2026-10-28 06:31 UTCVendor advisory
  10. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  11. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  12. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  13. 2026-10-25 14:10 UTCEG score recompute
  14. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  18. 2026-10-20 18:39 UTCEG score recompute
  19. 2026-10-20 18:39 UTCVendor advisory
  20. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  21. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  22. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  23. 2026-10-18 03:20 UTCEG score recompute
  24. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
Show 75 more
  1. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  3. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  4. 2026-10-13 10:47 UTCEG score recompute
  5. 2026-10-13 10:47 UTCVendor advisory
  6. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  7. 2026-10-12 15:45 UTCEG score recompute
  8. 2026-10-11 19:30 UTCEG score recompute
  9. 2026-10-11 16:46 UTCEG score recompute
  10. 2026-10-11 14:07 UTCEG score recompute
  11. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  12. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  13. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  14. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  16. 2026-10-06 23:48 UTCEG score recompute
  17. 2026-10-06 23:48 UTCVendor advisory
  18. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  19. 2026-10-05 19:52 UTCEG score recompute
  20. 2026-10-05 19:52 UTCVendor advisory
  21. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  22. 2026-10-04 23:49 UTCEG score recompute
  23. 2026-10-04 23:49 UTCVendor advisory
  24. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  25. 2026-10-04 06:26 UTCEG score recompute
  26. 2026-10-04 06:26 UTCVendor advisory
  27. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  28. 2026-10-03 02:45 UTCEG score recompute
  29. 2026-10-03 02:45 UTCVendor advisory
  30. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  31. 2026-10-02 10:29 UTCEG score recompute
  32. 2026-10-02 10:29 UTCVendor advisory
  33. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  34. 2026-10-01 13:58 UTCVendor advisory
  35. 2026-10-01 02:43 UTCEG score recompute
  36. 2026-10-01 02:43 UTCVendor advisory
  37. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  38. 2026-09-29 06:47 UTCEG score recompute
  39. 2026-09-29 06:47 UTCVendor advisory
  40. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  41. 2026-09-28 05:37 UTCVendor advisory
  42. 2026-09-27 18:22 UTCEG score recompute
  43. 2026-09-27 18:22 UTCVendor advisory
  44. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  45. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  46. 2026-09-25 04:50 UTCEG score recompute
  47. 2026-09-25 04:50 UTCVendor advisory
  48. 2026-09-24 08:42 UTCVendor advisory
  49. 2026-09-23 21:25 UTCEG score recompute
  50. 2026-09-23 21:25 UTCVendor advisory
  51. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  52. 2026-09-23 08:47 UTCVendor advisory
  53. 2026-09-22 21:32 UTCEG score recompute
  54. 2026-09-22 21:32 UTCVendor advisory
  55. 2026-09-22 07:08 UTCEG score recompute
  56. 2026-09-22 07:08 UTCVendor advisory
  57. 2026-09-20 20:59 UTCEG score recompute
  58. 2026-09-20 20:59 UTCVendor advisory
  59. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  60. 2026-09-20 01:12 UTCEG score recompute
  61. 2026-09-20 01:12 UTCVendor advisory
  62. 2026-09-19 13:43 UTCVendor advisory
  63. 2026-09-19 00:36 UTCEG score recompute
  64. 2026-09-19 00:36 UTCVendor advisory
  65. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  66. 2026-09-18 13:21 UTCVendor advisory
  67. 2026-09-18 01:15 UTCEG score recompute
  68. 2026-09-18 01:15 UTCVendor advisory
  69. 2026-09-17 01:23 UTCEG score recompute
  70. 2026-09-17 01:23 UTCVendor advisory
  71. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  72. 2026-09-16 05:24 UTCEG score recompute
  73. 2026-09-16 05:24 UTCVendor advisory
  74. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  75. 2026-09-15 02:56 UTCVendor advisory

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-67320?
CVE-2026-67320 is a high-severity vulnerability; its CVE record was 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 made public?
CVE-2026-67320 was made public on July 6, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 1, 2026. EchelonGraph's copy of the record carries a last-modified date of September 1, 2026; the record at its source may have been updated since.
Is CVE-2026-67320 actively exploited?
CVE-2026-67320 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-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?
A fix for CVE-2026-67320 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-67320 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-67320

Explore →

Is Your Infrastructure Affected by CVE-2026-67320?

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

Book a Demo →Browse All CVEs