Affects Google Chrome (widely deployed); allows sandbox escape and arbitrary code execution on Windows, risking mass endpoint compromise across organizations.
CVE-2026-87618
Chrome sandbox escape on Windows enabling arbitrary code execution.
Is CVE-2026-87618 being exploited?
Not confirmed. CVE-2026-87618 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.32% probability of exploitation in the next 30 days.
How severe is CVE-2026-87618?
CVE-2026-87618 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-87618?
Yes. A fix has been recorded for CVE-2026-87618. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-87618 affect?
CVE-2026-87618 affects Google Chrome on Windows <153.0.8010.36, Windows endpoints running affected Chrome builds. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-87618?
Update Chrome to 153.0.8010.36+ and restart browsers.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Arbitrary code execution outside Chrome sandbox on Windows via crafted HTML after renderer compromise.
Immediate action required
- affected< 153.0.8010.36
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.