Widespread Google Chrome browser; UAF allows code execution outside sandbox—urgent for all orgs using Chrome.
CVE-2026-95335
Chrome use-after-free in HID allows code execution outside sandbox.
Is CVE-2026-95335 being exploited?
Not confirmed. CVE-2026-95335 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-95335?
CVE-2026-95335 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-95335?
Yes. A fix has been recorded for CVE-2026-95335. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-95335 affect?
CVE-2026-95335 affects Google Chrome < 154.0.8037.57, Chrome Desktop (Windows, macOS, Linux). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-95335?
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.
Remote code execution outside Chrome sandbox via crafted HTML when renderer is compromised (sandbox escape).
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.