CVE-2026-67314

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.4% (32nd percentile of EPSS-scored CVEs). 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
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

axios versions >=1.15.2 and <1.18.0 contain prototype-pollution read-side gadgets in Basic auth subfield handling (lib/adapters/http.js and lib/helpers/resolveConfig.js). When an application is already affected by a separate prototype-pollution primitive and makes an axios request with an own auth object that omits the username and/or password properties, axios reads the inherited Object.prototype.username and Object.prototype.password values and uses them to construct an outbound 'Authorization: Basic ...' header. axios itself does not pollute prototypes. The practical impact is outbound request tampering: an attacker who controls the polluted prototype values can inject attacker-chosen Basic auth credentials or replace an existing Authorization header. Credential disclosure is only possible under additional application-specific conditions.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100CISA SSVC

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
Severity65% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

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 before 1.18.0 Prototype Pollution via auth subfields | Advisories | VulnCheck

https://www.vulncheck.com/advisories/axios-before-prototype-pollution-via-auth-subfields
github Patch Available🟡 PoC Available

Prototype pollution auth subfields can inject Basic auth · Advisory · axios/axios · GitHub

Affected: v1.15.2.

https://github.com/axios/axios/security/advisories/GHSA-xj6q-8x83-jv6g

Vendor Advisories for CVE-2026-67314(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:17885938432026-09-22redhat
redhatquay/quay-rhel9:17895637532026-09-21redhat
redhatsatellite/iop-vulnerability-frontend-rhel9:17896609692026-09-17redhat
redhatdevspaces/dashboard-rhel9:17891628842026-09-17redhat
redhatrhmtc/openshift-migration-ui-rhel8:17895463732026-09-17redhat
redhatsatellite/iop-vulnerability-frontend-rhel9:17896609832026-09-17redhat
redhatsatellite/iop-advisor-frontend-rhel9:17896595652026-09-17redhat
redhatquay/quay-rhel8:17885943762026-09-10redhat
redhatquay/quay-rhel8:17885618412026-09-09redhat
redhatquay/quay-rhel8:17885955742026-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
redhatrhacm2/console-rhel9:17873392482026-08-26redhat
redhatrhacm2/console-rhel9:17873392492026-08-26redhat
redhatopenshift-service-mesh/kiali-rhel9:17870771082026-08-25redhat
redhatopenshift-service-mesh/kiali-rhel9:17871656832026-08-25redhat
redhatgrafana13-1-main-13.1.1-0.5.2.hum12026-08-05redhat
redhatgrafana13-1-main-13.1.1-0.5.hum12026-08-03redhat
redhatjaeger-main-2.20.0-0.8.hum12026-07-30redhat

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 14× in last 7d / 67× 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 149 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2026-67314?
CVE-2026-67314 is a medium vulnerability published on August 1, 2026. axios versions >=1.15.2 and <1.18.0 contain prototype-pollution read-side gadgets in Basic auth subfield handling (lib/adapters/http.js and lib/helpers/resolveConfig.js). When an application is already affected by a separate prototype-pollution primitive and makes an axios request with an own auth…
When was CVE-2026-67314 disclosed?
CVE-2026-67314 was first published 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-67314 actively exploited?
CVE-2026-67314 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67314?
CVE-2026-67314 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-67314?
A fix for CVE-2026-67314 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-67314 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-67314

Explore →

Is Your Infrastructure Affected by CVE-2026-67314?

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

Book a Demo →Browse All CVEs