Affects widely-used Google Chrome; sandbox escape could lead to remote code execution across orgs.
CVE-2026-14113
Use-after-free in Chrome Updater on Windows enables sandbox escape via crafted HTML.
Is CVE-2026-14113 being exploited?
Not confirmed. CVE-2026-14113 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.31% probability of exploitation in the next 30 days.
How severe is CVE-2026-14113?
CVE-2026-14113 is rated Critical with a CVSS score of 9.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-14113?
Yes. A fix has been recorded for CVE-2026-14113. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-14113 affect?
CVE-2026-14113 affects Google Chrome (Windows), Chrome Updater (Windows). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-14113?
Update Chrome to the patched version with CVE fix.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Sandbox escape via compromised renderer could allow remote code execution on Windows Chrome.
Patch when possible
- affected< 150.0.7871.47
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.