Chrome is ubiquitous across enterprises; this sandbox-escaping RCE can lead to widespread endpoint compromise and is newsworthy for IT/security teams.
CVE-2026-102301
Out-of-bounds write in Chrome GPU allows code execution outside the sandbox.
Is CVE-2026-102301 being exploited?
Not confirmed. CVE-2026-102301 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-102301?
CVE-2026-102301 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-102301?
Yes. A fix has been recorded for CVE-2026-102301. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-102301 affect?
CVE-2026-102301 affects Google Chrome < 154.0.8037.92 (Desktop). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-102301?
Upgrade Chrome to 154.0.8037.92 or later immediately; enforce auto-updates.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Arbitrary code execution outside Chrome sandbox via crafted HTML/renderer exploit, enabling full user‑level compromise of affected endpoints.
Immediate action required
- affected< 154.0.8037.92
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.