Affects a widely used browser (Chrome) and could enable remote code execution across endpoints via sandbox escape, impacting many organizations.
CVE-2026-14412
ANGLE input validation flaw allows Chrome sandbox escape via crafted HTML.
Is CVE-2026-14412 being exploited?
Not confirmed. CVE-2026-14412 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.32% probability of exploitation in the next 30 days.
How severe is CVE-2026-14412?
CVE-2026-14412 is rated High with a CVSS score of 8.3. 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-14412?
Yes. A fix has been recorded for CVE-2026-14412. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-14412 affect?
CVE-2026-14412 affects Google Chrome (ANGLE) before 150.0.7871.46. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-14412?
Update Chrome to fixed version >=150.0.7871.46
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can escape Chrome's sandbox from a compromised renderer, potentially executing arbitrary code on user systems.
Patch when possible
- affected< 150.0.7871.46
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.