Google Chrome: Improper input validation in WebRTC
Summary
Improper input validation in the WebRTC component of Google Chrome allows a remote attacker to potentially execute arbitrary code inside the browser sandbox. The attacker needs a victim to open a crafted HTML page, so no login is required but user interaction is. Code execution is limited to the sandbox; no sandbox escape for this CVE is publicly known.
Affected
- Google Chrome prior to 156.0.8078.73
- Chromium-based browsers are not covered by this entry unless they have their own fix
Fixed in
- Google Chrome 156.0.8078.73 or later (Windows and Mac: 156.0.8078.73/.74; Linux: 156.0.8078.73)
- Fixed in the Stable channel update of 27 October 2026; newer Stable builds should be preferred
- Microsoft Edge: fix pending (Unknown)
- ChromeOS: no matching Stable update published yet (Unknown)
Workaround
- None known. The software update is the fix.
Exploitation
- CISA SSVC: exploitation none, automatable no, technical impact total
- No evidence of exploitation in the wild found at the time of research
- Not listed in the CISA KEV catalog
- No public proof of concept found
- EPSS: low (0.4 % according to the input data; values vary between sources)
Our recommendation
- Verify the Chrome version on all endpoints and update to at least 156.0.8078.73 (Windows/Mac .73 or .74), preferably the newest Stable build
- Force the update through the management console and track rollout status
- Check Microsoft Edge and ChromeOS devices for their own security updates
- Prioritise this patch because Chrome is used on all endpoints and the attack requires no login
- Re-check the Chromium bug and the NVD entry once details are public
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 570927027 issues.chromium.org
- CIS advisory for Google Chrome vulnerabilities www.cisecurity.org
- CVE-2026-118328 at threatint cve.threatint.com
- CVE-2026-118328 at Strix www.strix.ai
- OffSeq Radar: CVE-2026-118328 radar.offseq.com
- Chrome 156 security update overview (ChromeGeek) www.chromegeek.com
- Chrome security update October 2026 (Sandbanks Digital) sandbanksdigital.com
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, 09:55.
Original description (NVD)
Improper input validation in WebRTC in Google Chrome prior to 156.0.8078.73 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.