CVE-2026-67314

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 70% 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 — 3 sources updated this weekElevated
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.3Exploit: Elevated riskExposed: 0

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.3
EG Score
6.3(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity63% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

August 1, 2026

Last Modified

August 3, 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(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
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 19× in last 7d / 45× 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 01:53 UTCEG score recompute
  2. 2026-08-15 01:53 UTCVendor advisory
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-14 01:17 UTCEG score recompute
  5. 2026-08-14 01:17 UTCVendor advisory
  6. 2026-08-13 22:00 UTCEPSS rescore
  7. 2026-08-13 00:41 UTCEG score recompute
  8. 2026-08-13 00:41 UTCVendor advisory
  9. 2026-08-12 13:51 UTCEPSS rescore
  10. 2026-08-12 00:06 UTCEG score recompute
  11. 2026-08-12 00:06 UTCVendor advisory
  12. 2026-08-11 00:00 UTCEPSS rescore
  13. 2026-08-10 23:30 UTCVendor advisory
  14. 2026-08-09 22:54 UTCEG score recompute
  15. 2026-08-09 22:54 UTCVendor advisory
  16. 2026-08-09 13:47 UTCEPSS rescore
  17. 2026-08-08 22:19 UTCEG score recompute
  18. 2026-08-08 22:19 UTCVendor advisory
  19. 2026-08-08 16:37 UTCEPSS rescore
  20. 2026-08-07 21:43 UTCEG score recompute
  21. 2026-08-07 21:43 UTCVendor advisory
  22. 2026-08-06 21:07 UTCEG score recompute
  23. 2026-08-06 21:07 UTCVendor advisory
  24. 2026-08-06 21:07 UTCGHSA enrichment
  25. 2026-08-06 13:47 UTCEPSS rescore
Show 20 more
  1. 2026-08-05 20:31 UTCEG score recompute
  2. 2026-08-05 20:31 UTCVendor advisory
  3. 2026-08-05 20:31 UTCGHSA enrichment
  4. 2026-08-05 19:17 UTCEPSS rescore
  5. 2026-08-05 19:17 UTCEPSS rescore
  6. 2026-08-04 19:55 UTCEG score recompute
  7. 2026-08-04 19:55 UTCGHSA enrichment
  8. 2026-08-04 15:10 UTCEPSS rescore
  9. 2026-08-04 10:39 UTCEPSS rescore
  10. 2026-08-03 19:19 UTCEG score recompute
  11. 2026-08-03 19:19 UTCGHSA enrichment
  12. 2026-08-03 18:23 UTCEG score recompute
  13. 2026-08-03 18:23 UTCGHSA enrichment
  14. 2026-08-03 14:31 UTCEG score recompute
  15. 2026-08-03 14:31 UTCGHSA enrichment
  16. 2026-08-03 10:36 UTCEPSS rescore
  17. 2026-08-02 13:55 UTCGHSA enrichment
  18. 2026-08-01 13:19 UTCEG score recompute
  19. 2026-08-01 12:44 UTCEG score recompute
  20. 2026-08-01 12:42 UTCMITRE cvelistV5first tracked

Related CVEs(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 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-67314 actively exploited?
CVE-2026-67314 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 70.5% of all scored CVEs.
What is the CVSS score of CVE-2026-67314?
CVE-2026-67314 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-67314?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67314, 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-67314

Explore →

Is Your Infrastructure Affected by CVE-2026-67314?

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

Start Free Scan →Browse All CVEs