Widely used browser (Google Chrome). Sandbox-escape RCE from renderer compromise can lead to system-wide compromise; high CVSS and fixed update shipped.
CVE-2026-95354
Chrome use-after-free allows sandbox escape and remote code execution.
Is CVE-2026-95354 being exploited?
Not confirmed. CVE-2026-95354 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-95354?
CVE-2026-95354 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-95354?
Yes. A fix has been recorded for CVE-2026-95354. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-95354 affect?
CVE-2026-95354 affects Google Chrome (desktop) prior to 154.0.8037.57. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-95354?
Update Chrome to 154.0.8037.57 or later immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker can execute code outside Chrome's sandbox (RCE) by exploiting a renderer use-after-free via crafted network traffic.
Immediate action required
- 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.