Chrome is a ubiquitous browser; a remote code execution in the renderer via crafted HTML/CSS can impact many organizations and warrants broad IT distribution.
CVE-2026-106269
Use-after-free in Chrome CSS allows sandboxed remote code execution.
Is CVE-2026-106269 being exploited?
Not confirmed. CVE-2026-106269 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.27% probability of exploitation in the next 30 days.
How severe is CVE-2026-106269?
CVE-2026-106269 is rated High with a CVSS score of 8.8. 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-106269?
Yes. A fix has been recorded for CVE-2026-106269. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-106269 affect?
CVE-2026-106269 affects Google Chrome prior to 155.0.8059.39, Chrome Desktop (Windows/Mac/Linux). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-106269?
Update Chrome to 155.0.8059.39 or later; restrict untrusted web content.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote arbitrary code execution in Chrome's renderer via crafted HTML/CSS, enabling attacker-controlled code execution inside the sandbox.
Immediate action required
- affected< 155.0.8059.39
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.