Chrome is widely deployed; this high-severity sandbox escape via crafted web content can enable widespread browser-based RCE and user compromise.
CVE-2026-16807
Out-of-bounds write in Chrome codecs allows sandbox escape and potential remote code execution.
Is CVE-2026-16807 being exploited?
Not confirmed. CVE-2026-16807 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.43% probability of exploitation in the next 30 days.
How severe is CVE-2026-16807?
CVE-2026-16807 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-16807?
Yes. A fix has been recorded for CVE-2026-16807. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-16807 affect?
CVE-2026-16807 affects Google Chrome prior to 150.0.7871.186. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-16807?
Update Chrome to 150.0.7871.186 or later immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Out‑of‑bounds write in Chrome codecs can enable sandbox escape and remote code execution via crafted HTML/web content.
Immediate action required
- affected< 150.0.7871.186
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.