Affects Google Chrome/Chromium, a widely used browser; could disrupt IT ops with potential remote code execution.
CVE-2026-11629
Use-after-free in Chrome Ozone allows remote heap corruption via crafted HTML.
Is CVE-2026-11629 being exploited?
Not confirmed. CVE-2026-11629 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-11629?
CVE-2026-11629 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-11629?
Yes. A fix has been recorded for CVE-2026-11629. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-11629 affect?
CVE-2026-11629 affects Google Chrome (Chromium-based) <= 149.0.7827.102 with Ozone. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-11629?
Update Chrome to 149.0.7827.103+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via crafted HTML page due to Ozone heap corruption; potential full browser compromise.
Patch when possible
- affected< 149.0.7827.103
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.