CVE-2026-4450
Out-of-bounds write in Chrome V8 may cause heap corruption via crafted HTML.
Is CVE-2026-4450 being exploited?
Not confirmed. CVE-2026-4450 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.28% probability of exploitation in the next 30 days.
How severe is CVE-2026-4450?
CVE-2026-4450 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-4450?
Yes. A fix has been recorded for CVE-2026-4450. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-4450 affect?
CVE-2026-4450 affects Google Chrome browser (Desktop and mobile) before 146.0.7680.153. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-4450?
Update Chrome to 146.0.7680.153 or later
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution in the browser via heap corruption from a crafted HTML page; attacker could run arbitrary code on the host.
Patch when possible
- affected< 146.0.7680.153
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.