Chrome is a widely used browser; a sandbox-escape vulnerability enabling local code execution is high-impact and broadly relevant to IT/security teams.
CVE-2026-17699
Use-after-free in Chrome Views allows local sandbox escape via crafted file.
Is CVE-2026-17699 being exploited?
Not confirmed. CVE-2026-17699 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.24% probability of exploitation in the next 30 days.
How severe is CVE-2026-17699?
CVE-2026-17699 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-17699?
Yes. A fix has been recorded for CVE-2026-17699. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-17699 affect?
CVE-2026-17699 affects Google Chrome versions prior to 151.0.7922.72, Chromium-based browsers (where applicable). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-17699?
Update Chrome to 151.0.7922.72 or later immediately; restrict opening untrusted files.
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 malicious file, potentially enabling arbitrary code execution or privilege escalation on the host.
Patch when possible
- affected< 151.0.7922.72
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.