Chrome is a widely used browser; this flaw enables sandbox escape and arbitrary code execution on Windows, requiring broad, immediate attention from IT/security teams.
CVE-2026-87616
Chrome Views init flaw allows sandbox escape and arbitrary code execution on Windows.
Is CVE-2026-87616 being exploited?
Not confirmed. CVE-2026-87616 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.39% probability of exploitation in the next 30 days.
How severe is CVE-2026-87616?
CVE-2026-87616 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-87616?
Yes. A fix has been recorded for CVE-2026-87616. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-87616 affect?
CVE-2026-87616 affects Google Chrome (Windows) <153.0.8010.36, Microsoft Windows. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-87616?
Upgrade Chrome on Windows to 153.0.8010.36 or later immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can escape the Chrome renderer sandbox and execute arbitrary code on Windows via a crafted HTML page after social engineering.
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.