Wide-use of Google Chrome and a sandbox escape enabling remote code execution makes this organization-impacting and newsworthy.
CVE-2026-15773
Chrome use-after-free enables sandbox escape and remote code execution on Windows.
Is CVE-2026-15773 being exploited?
Not confirmed. CVE-2026-15773 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.37% probability of exploitation in the next 30 days.
How severe is CVE-2026-15773?
CVE-2026-15773 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-15773?
Yes. A fix has been recorded for CVE-2026-15773. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-15773 affect?
CVE-2026-15773 affects Google Chrome (Windows) < 150.0.7871.125. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-15773?
Update Chrome to 150.0.7871.125+ immediately; restrict untrusted HTML/JS.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Sandbox escape via crafted HTML allows remote attackers to execute arbitrary code on Windows hosts.
Immediate action required
- affected< 150.0.7871.125
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.