Widely-used Chrome browser; sandbox escape could lead to full host compromise; high-profile browser vulnerability.
CVE-2026-10889
Out-of-bounds read in ANGLE allows sandbox escape in Chrome.
Is CVE-2026-10889 being exploited?
Not confirmed. CVE-2026-10889 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.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-10889?
CVE-2026-10889 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-10889?
Yes. A fix has been recorded for CVE-2026-10889. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-10889 affect?
CVE-2026-10889 affects Google Chrome (ANGLE), Chromium-based browsers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-10889?
Patch Chrome to 149.0.7827.53+ immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Sandbox escape via crafted HTML after renderer compromise could enable remote code execution.
Immediate action required
- affected< 149.0.7827.53
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.