CVE-2026-125347: Google Chrome · Incorrect Authorization
Affects Google ChromeSource CVE Database V5
Not known to be exploited : upgrade to 157.0.8103.50 soon.
Data as of 10 Nov 2026, 17:47 UTC
Rated High by the CNA (Chrome) · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 157.0.8103.50
Exploitation evidence
Disclosed: evidence found.
CVE published 10 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 10 Nov 2026.
What to do
Upgrade Google Chrome to 157.0.8103.50.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleChrome | Affected
| Fixed in
|
AI-suggested
Apply the official update to Google Chrome version 157.0.8103.50 or later, which contains the fix for this vulnerability.
Description
An incorrect authorization vulnerability in the FileSystem component of Google Chrome prior to version 157.0.8103.50 allows a remote attacker to execute arbitrary code outside the sandbox by tricking a user into visiting a crafted HTML page. This issue has been fixed in version 157.0.8103.50.