Skip to content
major vulnerability· requires attention

Chrome is widely deployed; this is a sandbox escape allowing arbitrary code execution outside the renderer, posing enterprise-wide risk if unpatched.

Applications

CVE-2026-87537

8.1
High
EPSS 0.30%Patch availableSep 10, 2026

Chrome sandbox escape enabling code execution outside renderer via crafted network traffic

common questions

Is CVE-2026-87537 being exploited?

Not confirmed. CVE-2026-87537 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-87537?

CVE-2026-87537 is rated High with a CVSS score of 8.1. 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-87537?

Yes. A fix has been recorded for CVE-2026-87537. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-87537 affect?

CVE-2026-87537 affects Google Chrome < 153.0.8010.36 (Windows, macOS, Linux). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-87537?

Update Chrome to 153.0.8010.36 or later; enforce extension policies; monitor endpoints

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Google Chrome < 153.0.8010.36 (Windows, macOS, Linux)
impact

Remote code execution outside Chrome sandbox by a compromised renderer via crafted network traffic, enabling arbitrary code, persistence, and lateral movement.

action required

Immediate action required

affected versions
Google Chrome
  • 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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free