Google Chrome is widely deployed; this RCE allows code execution outside the Chrome sandbox if the renderer is compromised, posing broad endpoint compromise risk that merits company-wide attention.
CVE-2026-95348
Chrome Bluetooth use-after-free allows RCE outside sandbox (pre-154.0.8037.57)
Is CVE-2026-95348 being exploited?
Not confirmed. CVE-2026-95348 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-95348?
CVE-2026-95348 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-95348?
Yes. A fix has been recorded for CVE-2026-95348. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-95348 affect?
CVE-2026-95348 affects Google Chrome (Desktop) <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-95348?
Upgrade Chrome to 154.0.8037.57+ 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 after renderer compromise.
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.