Widespread Chrome sandbox escape with potential RCE; affects a widely used product across industries.
CVE-2026-11047
Chrome Windows sandbox escape via crafted HTML page (pre 149.0.7827.53)
Is CVE-2026-11047 being exploited?
Not confirmed. CVE-2026-11047 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.30% probability of exploitation in the next 30 days.
How severe is CVE-2026-11047?
CVE-2026-11047 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-11047?
Yes. A fix has been recorded for CVE-2026-11047. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-11047 affect?
CVE-2026-11047 affects Google Chrome on Windows (before 149.0.7827.53). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-11047?
Patch Chrome to 149.0.7827.53 or newer
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
RCE via sandbox escape: compromised renderer can run arbitrary code on Windows.
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.