CVE-2026-131041: Google Chrome · Improper Input Validation
Affects Google ChromeSource CVE Database V5
Not known to be exploited : upgrade to 158.0.8127.36 when convenient.
Data as of 17 Nov 2026, 21:19 UTC
Rated Low by the CNA (Chrome) · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 158.0.8127.36
Exploitation evidence
Disclosed: evidence found.
CVE published 17 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 17 Nov 2026.
What to do
Upgrade Google Chrome to 158.0.8127.36.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleChrome | Affected
| Fixed in
|
AI-suggested
Update Google Chrome to version 158.0.8127.36 or later, where this vulnerability has been fixed. No additional mitigation steps are required as the issue is resolved in the official patch.
Description
An improper input validation vulnerability in the Editing component of Google Chrome prior to version 158.0.8127.36 could allow a remote attacker to potentially bypass the web origin policy using a crafted HTML page. The issue has been fixed in version 158.0.8127.36. The Chromium security team rates this vulnerability as low severity.