Widely used Chrome browser; sandbox escape via crafted video could lead to system compromise across many orgs.
CVE-2026-8573
Chrome Windows: codec overflow may allow sandbox escape.
Is CVE-2026-8573 being exploited?
Not confirmed. CVE-2026-8573 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.23% probability of exploitation in the next 30 days.
How severe is CVE-2026-8573?
CVE-2026-8573 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-8573?
Yes. A fix has been recorded for CVE-2026-8573. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-8573 affect?
CVE-2026-8573 affects Google Chrome on Windows prior to 148.0.7778.168. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-8573?
Patch to latest Chrome build with fix
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker could escape Chrome sandbox via crafted video file, risking code execution on affected Windows hosts.
Immediate action required
- affected< 148.0.7778.168
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.