Chrome is widely deployed; a sandbox escape enabling host compromise is high-impact across enterprises and consumer endpoints.
CVE-2026-17692
Chrome DataTransfer use-after-free allows renderer sandbox escape.
Is CVE-2026-17692 being exploited?
Not confirmed. CVE-2026-17692 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.49% probability of exploitation in the next 30 days.
How severe is CVE-2026-17692?
CVE-2026-17692 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-17692?
Yes. A fix has been recorded for CVE-2026-17692. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-17692 affect?
CVE-2026-17692 affects Google Chrome on Windows prior to 151.0.7922.72. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-17692?
Update Chrome to 151.0.7922.72 or later immediately; restrict renderer privileges.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted HTML can trigger a use-after-free to escape the Chrome renderer sandbox, enabling arbitrary code execution on the host.
Immediate action required
- 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.