CVE-2026-14109

CRITICALNVD 9.69.6—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
9.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.6Exploit: NoneExposed: 0

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

Insufficient policy enforcement in Mojo in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Low)

CVSS v3
9.6
EG Score
9.6(high)
EPSS
16.5%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 2, 2026

Advisory Details (2)

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

Chromium

https://issues.chromium.org/issues/513694957
generic

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html

Vendor Advisories for CVE-2026-14109(1)

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

Weakness Classification(2)

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

Frequently asked(5)

What is CVE-2026-14109?
CVE-2026-14109 is a critical vulnerability published on July 1, 2026. Insufficient policy enforcement in Mojo in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Low)
When was CVE-2026-14109 disclosed?
CVE-2026-14109 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-14109 actively exploited?
CVE-2026-14109 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 16.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-14109?
CVE-2026-14109 has a CVSS v3 base score of 9.6 (NVD).
How do I remediate CVE-2026-14109?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14109, 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-14109

Explore →

Is Your Infrastructure Affected by CVE-2026-14109?

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

Start Free Scan →Browse All CVEs