Affects Google Chrome, a ubiquitous browser. Sandbox escape enabling host code execution is high-impact across organizations and merits broad distribution.
CVE-2026-17837
Chrome DevTools sandbox escape via crafted HTML allows host compromise
Is CVE-2026-17837 being exploited?
Not confirmed. CVE-2026-17837 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-17837?
CVE-2026-17837 is rated Critical with a CVSS score of 9.6. 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-17837?
Yes. A fix has been recorded for CVE-2026-17837. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-17837 affect?
CVE-2026-17837 affects Google Chrome < 151.0.7922.72, Chromium-based browsers (potentially). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-17837?
Upgrade Chrome to 151.0.7922.72+ immediately; enforce EDR and restrict untrusted content.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
A compromised renderer plus crafted HTML can escape DevTools sandbox to execute code on the host and access user data (RCE/data theft).
Immediate action required
- affected< 151.0.7922.72
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.