Chrome is ubiquitous; an RCE that escapes the sandbox can lead to widespread host compromise across enterprises and must be broadly communicated.
CVE-2026-95341
Chrome Desktop input-validation flaw enables sandbox escape and arbitrary code execution.
Is CVE-2026-95341 being exploited?
Not confirmed. CVE-2026-95341 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-95341?
CVE-2026-95341 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-95341?
Yes. A fix has been recorded for CVE-2026-95341. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-95341 affect?
CVE-2026-95341 affects Google Chrome Desktop < 154.0.8037.57 (Windows/macOS/Linux). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-95341?
Update Chrome to 154.0.8037.57+ immediately; monitor endpoints.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Compromised renderer can use crafted network traffic to execute arbitrary code outside Chrome's sandbox, enabling host takeover.
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.