CVE-2026-16413
Out-of-bounds write in ANGLE may allow Chrome sandbox escape (pre-150.0.7871.182).
Is CVE-2026-16413 being exploited?
Not confirmed. CVE-2026-16413 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.26% probability of exploitation in the next 30 days.
How severe is CVE-2026-16413?
CVE-2026-16413 is rated High with a CVSS score of 8.3. 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-16413?
Yes. A fix has been recorded for CVE-2026-16413. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-16413 affect?
CVE-2026-16413 affects Google Chrome <150.0.7871.182, Chromium-based browsers (may be affected). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-16413?
Update Chrome/Chromium to 150.0.7871.182 or later immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Renderer-level out-of-bounds write enabling sandbox escape via crafted HTML, potentially leading to arbitrary code execution on the host.
Immediate action required
- affected< 150.0.7871.182
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.