Widespread Chrome browser; sandbox escape risk could impact endpoints across industries.
CVE-2026-13829
Chrome Windows sandbox escape via crafted HTML page due to input validation flaw.
Is CVE-2026-13829 being exploited?
Not confirmed. CVE-2026-13829 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.32% probability of exploitation in the next 30 days.
How severe is CVE-2026-13829?
CVE-2026-13829 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-13829?
Yes. A fix has been recorded for CVE-2026-13829. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-13829 affect?
CVE-2026-13829 affects Google Chrome for Windows (pre-150.0.7871.47). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-13829?
Update to 150.0.7871.47+ and restart
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote sandbox escape from a crafted page could allow code execution with Chrome privileges.
Immediate action required
- affected< 150.0.7871.47
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.