Chromium-based Chrome is widely used; sandbox escape could yield RCE on Windows across enterprises.
CVE-2026-13920
Chrome Windows: sandbox escape via crafted HTML due to input validation flaw.
Is CVE-2026-13920 being exploited?
Not confirmed. CVE-2026-13920 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.34% probability of exploitation in the next 30 days.
How severe is CVE-2026-13920?
CVE-2026-13920 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-13920?
Yes. A fix has been recorded for CVE-2026-13920. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-13920 affect?
CVE-2026-13920 affects Google Chrome for Windows < 150.0.7871.47. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-13920?
Update to latest Chrome; enable auto-update.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution by escaping the Chrome sandbox from a compromised renderer via crafted HTML page.
Immediate action required
- affected< 150.0.7871.47
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.