Affects widely-used Chrome browser; sandbox escape could enable remote code execution, impacting many organizations.
CVE-2026-11671
Use-after-free in Chrome navigation enables sandbox escape via crafted HTML.
Is CVE-2026-11671 being exploited?
Not confirmed. CVE-2026-11671 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.24% probability of exploitation in the next 30 days.
How severe is CVE-2026-11671?
CVE-2026-11671 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-11671?
Yes. A fix has been recorded for CVE-2026-11671. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-11671 affect?
CVE-2026-11671 affects Google Chrome < 149.0.7827.103, Chromium-based browsers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-11671?
Patch Chrome to the latest version.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker could escape Chrome sandbox via crafted HTML page, potentially executing code on user system.
Immediate action required
- affected< 149.0.7827.103
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.