Skip to content
major vulnerability· requires attention

Widely deployed Google Chrome; critical RCE with sandbox escape on Windows risks mass compromise across organizations.

Applications

CVE-2026-87528

9.6
Critical
EPSS 0.35%Patch availableSep 9, 2026

Chrome RCE & sandbox escape via Rust type confusion (Windows <153.0.8010.36)

common questions

Is CVE-2026-87528 being exploited?

Not confirmed. CVE-2026-87528 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.35% probability of exploitation in the next 30 days.

How severe is CVE-2026-87528?

CVE-2026-87528 is rated Critical with a CVSS score of 9.6. 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-87528?

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

What does CVE-2026-87528 affect?

CVE-2026-87528 affects Google Chrome on Windows <153.0.8010.36. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-87528?

Update Chrome to 153.0.8010.36 or later immediately; monitor endpoints and block exploit indicators.

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

executive summary
technical analysis
affected
Google Chrome on Windows <153.0.8010.36
impact

Remote code execution and sandbox escape via crafted HTML, enabling arbitrary code execution as the user on Windows.

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