CVE-2026-118328: Google Chrome · Improper Input Validation
Affects Google ChromeSource CVE Database V5
Not known to be exploited : upgrade to 156.0.8078.73 soon.
Data as of 27 Oct 2026, 23:42 UTC
Rated High by the CNA (Chrome) · CVSS not yet scored by NVD
- Patch
- Available – fixed in 156.0.8078.73
Exploitation evidence
Disclosed: evidence found.
CVE published 27 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade Google Chrome to 156.0.8078.73.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleChrome | Affected
| Fixed in
|
AI-suggested
Users should update Google Chrome to version 156.0.8078.73 or later to remediate this vulnerability. The vendor has released an official fix, and applying this update will mitigate the risk.
Description
An improper input validation vulnerability in the WebRTC component of Google Chrome prior to version 156.0.8078.73 allows a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. This vulnerability has been assigned high severity by Chromium security. A fix is available in Chrome version 156.0.8078.73.