Google Chrome is ubiquitous; a WebUI sandbox escape enabling host code execution can lead to widespread compromise and requires org-wide mitigation.
CVE-2026-87506
Chrome WebUI sandbox escape allows code execution outside renderer sandbox.
Is CVE-2026-87506 being exploited?
Not confirmed. CVE-2026-87506 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-87506?
CVE-2026-87506 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-87506?
Yes. A fix has been recorded for CVE-2026-87506. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-87506 affect?
CVE-2026-87506 affects Google Chrome <153.0.8010.36 (desktop), Windows, macOS, Linux. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-87506?
Update Chrome to 153.0.8010.36 or later immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Escalation from a compromised renderer to arbitrary code execution outside Chrome's sandbox, enabling host compromise, data theft, and persistence.
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.