CVE-2026-121237: Google Chrome · Improper State Validation
Affects Google ChromeSource CVE Database V5
Not known to be exploited : upgrade to 157.0.8103.38 when convenient.
Data as of 3 Nov 2026, 21:14 UTC
Rated Medium by the CNA (Chrome) · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 157.0.8103.38
Exploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Upgrade Google Chrome to 157.0.8103.38.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleChrome | Affected
| Fixed in
|
AI-suggested
Update Google Chrome to version 157.0.8103.38 or later, where this vulnerability is fixed. No other mitigation is required as the issue is resolved in the official release.
Description
An improper state validation vulnerability in the FileSystem component of Google Chrome prior to version 157.0.8103.38 allows a remote attacker to bypass system access restrictions via a crafted HTML page leveraging social engineering. The issue has been fixed in Chrome version 157.0.8103.38. The vulnerability is rated with medium severity by Chromium security.