Chrome is widely deployed; a sandbox escape enabling code execution on Windows is broadly impactful and newsworthy for IT teams.
CVE-2026-102317
Chrome on Windows local sandbox escape allowing arbitrary code execution outside the sandbox.
Is CVE-2026-102317 being exploited?
Not confirmed. CVE-2026-102317 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-102317?
CVE-2026-102317 is rated High with a CVSS score of 8.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-102317?
Yes. A fix has been recorded for CVE-2026-102317. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-102317 affect?
CVE-2026-102317 affects Google Chrome for Windows < 154.0.8037.92. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-102317?
Update Chrome on Windows to 154.0.8037.92+ and limit untrusted local code access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local attacker can escape Chrome's sandbox via a local program to execute arbitrary code on Windows, enabling privilege escalation.
Patch when possible
- affected< 154.0.8037.92
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.