CVE-2026-6311
Chrome Windows sandbox escape via crafted HTML in a compromised renderer.
Is CVE-2026-6311 being exploited?
Not confirmed. CVE-2026-6311 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.27% probability of exploitation in the next 30 days.
How severe is CVE-2026-6311?
CVE-2026-6311 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-6311?
Yes. A fix has been recorded for CVE-2026-6311. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-6311 affect?
CVE-2026-6311 affects Google Chrome (Windows) <= 147.0.7727.101. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-6311?
Update to 147.0.7727.101 or newer
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Sandbox escape enabling code execution on Windows from a compromised Chrome renderer.
Patch when possible
- affected< 147.0.7727.101
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.