Widely used Google Chrome; vulnerability enables sandbox escape and arbitrary code execution—high-impact for many enterprises and likely to be broadly noticed.
CVE-2026-95274
Chrome DevTools encoding bug allows sandbox escape and arbitrary code execution.
Is CVE-2026-95274 being exploited?
Not confirmed. CVE-2026-95274 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.38% probability of exploitation in the next 30 days.
How severe is CVE-2026-95274?
CVE-2026-95274 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-95274?
Yes. A fix has been recorded for CVE-2026-95274. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-95274 affect?
CVE-2026-95274 affects Google Chrome < 154.0.8037.57 (Desktop). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-95274?
Update Chrome to 154.0.8037.57 or later across endpoints immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
A renderer-compromised attacker can escape the sandbox and execute arbitrary code on the host via crafted HTML.
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.