CVE-2026-15120
Use-after-free in Chrome (Windows) allows sandbox escape from renderer.
Is CVE-2026-15120 being exploited?
Not confirmed. CVE-2026-15120 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.30% probability of exploitation in the next 30 days.
How severe is CVE-2026-15120?
CVE-2026-15120 is rated High with a CVSS score of 8.3. 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-15120?
Yes. A fix has been recorded for CVE-2026-15120. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-15120 affect?
CVE-2026-15120 affects Google Chrome on Windows prior to 150.0.7871.115. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-15120?
Update Chrome to 150.0.7871.115 or later immediately and verify endpoint versions.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Sandbox escape via crafted HTML enabling arbitrary code execution on host if renderer is compromised.
Immediate action required
- affected< 150.0.7871.115
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.