Chrome is a widely used desktop/browser platform; a remote use-after-free enabling heap corruption/RCE on many endpoints is broadly impactful and must be broadly communicated.
CVE-2026-15129
Use-after-free in Chrome Views enabling heap corruption and potential remote code execution.
Is CVE-2026-15129 being exploited?
Not confirmed. CVE-2026-15129 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.34% probability of exploitation in the next 30 days.
How severe is CVE-2026-15129?
CVE-2026-15129 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-15129?
Yes. A fix has been recorded for CVE-2026-15129. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-15129 affect?
CVE-2026-15129 affects Google Chrome prior to 150.0.7871.115, Chromium-based browsers (potentially). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-15129?
Upgrade Chrome to 150.0.7871.115 or later immediately; enforce enterprise updates.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can trigger heap corruption via crafted HTML, potentially achieving arbitrary code execution in the browser process.
Immediate action required
- affected< 150.0.7871.115
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.