Skip to content
major vulnerability· requires attention

Remote code execution in Google Chrome (widely deployed browser) allowing code outside the sandbox; affects large user base and risks widespread compromise.

Applications

CVE-2026-95331

9.6
Critical
EPSS n/aPatch availableSep 30, 2026

RCE via ANGLE out-of-bounds write in Chrome <154.0.8037.57

common questions

Is CVE-2026-95331 being exploited?

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

How severe is CVE-2026-95331?

CVE-2026-95331 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-95331?

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

What does CVE-2026-95331 affect?

CVE-2026-95331 affects Google Chrome (Desktop) < 154.0.8037.57, Chromium-based browsers may be affected. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-95331?

Update Chrome to 154.0.8037.57+ immediately; block or isolate unpatched clients.

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

executive summary
technical analysis
affected
Google Chrome (Desktop) < 154.0.8037.57Chromium-based browsers may be affected
impact

Remote attacker can execute arbitrary code outside Chrome's sandbox via crafted HTML, enabling full system compromise on vulnerable hosts.

action required

Immediate action required

affected versions
Google Chrome
  • affected< 154.0.8037.57

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