Skip to content
major vulnerability· requires attention

Remote code execution in Google Chrome's V8 affects a ubiquitous browser used enterprise-wide; widespread impact and urgent patching warranted.

Web

CVE-2026-87491

8.8
High
KEV · Exploited in wildEPSS 1.00%Patch availableSep 9, 2026

OOB write in V8 enabling remote code execution in Chrome <153.0.8010.36

common questions

Is CVE-2026-87491 being exploited?

Yes. CVE-2026-87491 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2026-87491?

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

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

What does CVE-2026-87491 affect?

CVE-2026-87491 affects Google Chrome (desktop) prior to 153.0.8010.36, Chromium-based browsers (potentially). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-87491?

Update Chrome to 153.0.8010.36+ immediately and enforce browser auto-updates

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

executive summary
technical analysis
affected
Google Chrome (desktop) prior to 153.0.8010.36Chromium-based browsers (potentially)
impact

Remote code execution via crafted HTML exploiting an out-of-bounds write in V8; attacker can run code inside Chrome sandbox, risking host compromise if sandbox is escaped.

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