Widely-used Chrome browser; sandbox escape could lead to arbitrary code execution.
CVE-2026-11640
Chrome renderer sandbox escape via libyuv integer overflow.
Is CVE-2026-11640 being exploited?
Not confirmed. CVE-2026-11640 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.23% probability of exploitation in the next 30 days.
How severe is CVE-2026-11640?
CVE-2026-11640 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-11640?
Yes. A fix has been recorded for CVE-2026-11640. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-11640 affect?
CVE-2026-11640 affects Google Chrome (<149.0.7827.103). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-11640?
Upgrade to Chrome 149.0.7827.103 or newer.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can escape the renderer sandbox via crafted HTML, enabling arbitrary code execution.
Patch when possible
- 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.