Skip to content
major vulnerability· requires attention

Chrome is widely deployed; an RCE that escapes the sandbox on Windows can lead to large-scale system compromise across organizations.

Applications

CVE-2026-84351

8.3
High
EPSS 0.28%Patch availableSep 2, 2026

Chrome GPU buffer overflow allows code execution outside sandbox on Windows.

common questions

Is CVE-2026-84351 being exploited?

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

How severe is CVE-2026-84351?

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

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

What does CVE-2026-84351 affect?

CVE-2026-84351 affects Google Chrome on Windows (versions prior to 152.0.7977.75). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-84351?

Update Chrome to 152.0.7977.75 or later immediately.

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 (versions prior to 152.0.7977.75)
impact

Remote arbitrary code execution outside Chrome sandbox via crafted HTML after renderer compromise, enabling system-level compromise.

action required

Immediate action required

affected versions
Google Chrome
  • affected< 152.0.7977.75

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