Chrome is widely deployed; sandbox escape enabling local code execution can lead to host compromise across organizations.
CVE-2026-93375
Local sandbox escape in Chrome Tracing on Windows before 153.0.8010.52.
Is CVE-2026-93375 being exploited?
Not confirmed. CVE-2026-93375 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.
How severe is CVE-2026-93375?
CVE-2026-93375 is rated High with a CVSS score of 8.1. 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-93375?
Yes. A fix has been recorded for CVE-2026-93375. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-93375 affect?
CVE-2026-93375 affects Google Chrome for Windows < 153.0.8010.52, Windows desktops/laptops running affected Chrome. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-93375?
Update Chrome on Windows to 153.0.8010.52 or later immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local attacker can escape Chrome sandbox and execute arbitrary code on Windows, enabling system compromise or persistence.
Immediate action required
- affected< 153.0.8010.52
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.