Google Chrome: Improper state validation in DevTools
Summary
Improper state validation in the DevTools component of Google Chrome before 155.0.8059.39 can be triggered by a crafted HTML page. A remote attacker could potentially execute arbitrary code inside the browser sandbox. The attack requires that a user visits the malicious page, and the NVD record gives no further exploit details.
Affected
- Google Chrome prior to 155.0.8059.39 (NVD description)
- Third-party reports give Windows and macOS builds before 155.0.8059.39/.40 and Linux builds before 155.0.8059.39 (not verified against Google's advisory)
- Chromium-based products such as Microsoft Edge may be affected; check their vendor advisories
Fixed in
- Google Chrome 155.0.8059.39/.40 for Windows and macOS, 155.0.8059.39 for Linux (Stable release of 6 Oct 2026, per third-party reports)
- Newer Chrome 155 builds are available and should be preferred (reported: 155.0.8059.84/.85 for Windows and macOS, 155.0.8059.84 for Linux)
Workaround
- Unknown. No vendor workaround is recorded in the sources reviewed.
- Chrome enterprise policies can restrict DevTools on managed devices (general hardening, not verified for this CVE).
Exploitation
- CISA SSVC assessment: exploitation none, not automatable, total technical impact.
- No evidence of active exploitation or public proof of concept found; not listed as known exploited.
Our recommendation
- Check the Chrome version on all endpoints and confirm that the managed update channel is active.
- Update to the latest Chrome 155 build, at least 155.0.8059.39/.40 (Windows, macOS) or 155.0.8059.39 (Linux).
- Check Microsoft Edge and other Chromium-based browsers separately.
- Monitor vendor advisories for reports of exploitation.
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- Chrome Releases: Stable Channel Update for Desktop chromereleases.googleblog.com
- Chromium issue tracker entry issues.chromium.org
- Strix CVE record www.strix.ai
- CIS advisory: multiple vulnerabilities in Google Chrome www.cisecurity.org
- Horus Valley: Chrome 155 security update www.horusvalley.com
- Windows Forum: Chrome 155.0.8059.79/.80 fixes windowsforum.com
- GBHackers: Chrome 155 security flaws gbhackers.com
- HKCERT: Microsoft Edge multiple vulnerabilities www.hkcert.org
Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 31 Oct 2026, 21:50.
Original description (NVD)
Improper state validation in DevTools in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Sources
The tracker combines official, freely usable data sources – updated continuously:
- NVD (NIST) – CVEs, rating (CVSS), affected products
- CISA KEV – vulnerabilities confirmed by CISA as actively exploited
- CISA Vulnrichment – CISA assessment (SSVC) in the official CVE record
- FIRST EPSS – probability of exploitation
- Microsoft MSRC – Patch Tuesday: vulnerabilities, severity, updates
- PoC-in-GitHub – public proof-of-concept repositories
- Metasploit (Rapid7) – modules of the Metasploit Framework
- Exploit-DB (OffSec) – archive of public exploits (links only)
- Patch days: official vendor pages (linked per vendor) (Vendor patch days)
This product uses data from the NVD API but is not endorsed or certified by the NVD. EPSS data © FIRST.org.
Affected? We can help.
We check whether your systems are affected, install updates and close the gap – continuously with the System Health Checker if you wish.