CVE-2026-14105

MEDIUMNVD 4.39.6
EchelonGraph scoreMEDIUM confidence

Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-01. NVD baseline CVSS 4.3; sources differ by 5.3.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
4.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Insufficient policy enforcement in Speech in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to bypass same origin policy via a crafted HTML page. (Chromium security severity: Low)

CVSS v3
4.3
EG Score
9.6(medium)
EPSS
6.3%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 2, 2026

Advisory Details (2)

Auto-updated Jul 1, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-14105(1)

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

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 62× in last 7d / 62× 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-07-07 01:22 UTCEG score recompute
  2. 2026-07-07 01:22 UTCVendor advisory
  3. 2026-07-07 01:22 UTCGHSA enrichment
  4. 2026-07-06 21:17 UTCEG score recompute
  5. 2026-07-06 21:17 UTCVendor advisory
  6. 2026-07-06 21:17 UTCGHSA enrichment
  7. 2026-07-06 17:10 UTCEG score recompute
  8. 2026-07-06 17:10 UTCVendor advisory
  9. 2026-07-06 17:10 UTCGHSA enrichment
  10. 2026-07-06 16:27 UTCEPSS rescore
  11. 2026-07-06 13:05 UTCEG score recompute
  12. 2026-07-06 13:05 UTCVendor advisory
  13. 2026-07-06 13:05 UTCGHSA enrichment
  14. 2026-07-06 09:00 UTCEG score recompute
  15. 2026-07-06 09:00 UTCVendor advisory
  16. 2026-07-06 09:00 UTCGHSA enrichment
  17. 2026-07-06 04:50 UTCEG score recompute
  18. 2026-07-06 04:50 UTCVendor advisory
  19. 2026-07-06 04:50 UTCGHSA enrichment
  20. 2026-07-06 02:23 UTCEPSS rescore
  21. 2026-07-06 00:44 UTCEG score recompute
  22. 2026-07-06 00:44 UTCVendor advisory
  23. 2026-07-06 00:44 UTCGHSA enrichment
  24. 2026-07-05 20:39 UTCEG score recompute
  25. 2026-07-05 20:39 UTCVendor advisory
Show 37 more
  1. 2026-07-05 20:39 UTCGHSA enrichment
  2. 2026-07-05 16:33 UTCEG score recompute
  3. 2026-07-05 16:33 UTCVendor advisory
  4. 2026-07-05 16:33 UTCGHSA enrichment
  5. 2026-07-05 12:28 UTCEG score recompute
  6. 2026-07-05 12:28 UTCVendor advisory
  7. 2026-07-05 12:28 UTCGHSA enrichment
  8. 2026-07-05 08:23 UTCEG score recompute
  9. 2026-07-05 08:23 UTCVendor advisory
  10. 2026-07-05 08:23 UTCGHSA enrichment
  11. 2026-07-05 04:18 UTCEG score recompute
  12. 2026-07-05 04:18 UTCVendor advisory
  13. 2026-07-05 04:18 UTCGHSA enrichment
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-05 02:30 UTCEPSS rescore
  16. 2026-07-05 00:12 UTCEG score recompute
  17. 2026-07-05 00:12 UTCVendor advisory
  18. 2026-07-05 00:12 UTCGHSA enrichment
  19. 2026-07-04 20:07 UTCEG score recompute
  20. 2026-07-04 20:07 UTCVendor advisory
  21. 2026-07-04 20:07 UTCGHSA enrichment
  22. 2026-07-04 16:03 UTCEG score recompute
  23. 2026-07-04 16:03 UTCVendor advisory
  24. 2026-07-04 16:02 UTCGHSA enrichment
  25. 2026-07-04 11:57 UTCEG score recompute
  26. 2026-07-04 11:57 UTCVendor advisory
  27. 2026-07-04 11:57 UTCGHSA enrichment
  28. 2026-07-04 07:53 UTCEG score recompute 9.60
  29. 2026-07-04 07:53 UTCVendor advisory
  30. 2026-07-04 07:52 UTCGHSA enrichment
  31. 2026-07-04 06:31 UTCEPSS rescore
  32. 2026-07-02 16:58 UTCNVD updateCVSS v3 → 4.3 · severity → MEDIUM
  33. 2026-07-01 19:07 UTCNVD updateCVSS v3 → 9.6 · severity → CRITICAL
  34. 2026-07-01 15:06 UTCEPSS rescore
  35. 2026-07-01 15:06 UTCEPSS rescore
  36. 2026-07-01 01:22 UTCEG score recompute
  37. 2026-07-01 01:22 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-14105?
CVE-2026-14105 is a medium vulnerability published on July 1, 2026. Insufficient policy enforcement in Speech in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to bypass same origin policy via a crafted HTML page. (Chromium security severity: Low)
When was CVE-2026-14105 disclosed?
CVE-2026-14105 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14105 actively exploited?
CVE-2026-14105 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-14105?
CVE-2026-14105 has a CVSS v3 base score of 4.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.6.
How do I remediate CVE-2026-14105?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14105, 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

Explore the affected products and dependency analysis for CVE-2026-14105

Explore →

Is Your Infrastructure Affected by CVE-2026-14105?

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