Google Chrome: Use after free in WebRTC allows code execution in sandbox
Summary
A use-after-free flaw in the WebRTC component of Google Chrome allows a remote attacker to execute arbitrary code inside the Chrome sandbox. The attacker needs the victim to visit a crafted HTML page, and no login is required. Full compromise would also need a sandbox escape, which this description does not cover. No in-the-wild exploitation or public proof-of-concept was found.
Affected
- Google Chrome desktop prior to 156.0.8078.47 (CVE record and vendor advisory)
- Chromium-based browsers that ingest the fix, such as Microsoft Edge prior to 156.0.4314.42 (one third-party advisory, not verified against the Microsoft advisory)
- Android Chrome builds prior to 156.0.8078.47 (third-party report)
- Linux distribution Chromium packages: Unknown.
Fixed in
- Chrome 156.0.8078.47 for Linux
- Chrome 156.0.8078.47 or 156.0.8078.48 for Windows and macOS
- Microsoft Edge 156.0.4314.42 or later (third-party advisory)
- Linux distributions: Unknown, verify with the distribution security tracker.
Workaround
Unknown. No workaround is known; apply the browser update and restart the browser.
Exploitation
- CISA SSVC: Exploitation none, Automatable no, Technical Impact total.
- No evidence of exploitation in the wild was found; the CISA KEV status was not verified.
- No public proof-of-concept was found.
- EPSS score reported as 0.0056 (low).
Our recommendation
- Inventory all Chrome, Edge and other Chromium-based browsers and their versions.
- Update Chrome to 156.0.8078.47 or later (Linux) or 156.0.8078.47/.48 or later (Windows and macOS), and Edge to 156.0.4314.42 or later.
- Restart browsers after the update, as the old process may still run.
- For distribution-packaged Chromium, check the vendor tracker for a fixed build and check installed snap versions on Ubuntu.
- Prioritise staff endpoints with high web exposure.
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 issues.chromium.org
- Strix CVE record www.strix.ai
- Ubuntu security notice ubuntu.com
- Vulners MSCVE entry (Edge, EPSS) vulners.com
- HKCERT security bulletin (Microsoft Edge) www.hkcert.org
- Cybersecurity News: Chrome 156 security update cybersecuritynews.com
- Penligent: Chrome 156 security update www.penligent.ai
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, 13:31.
Original description (NVD)
Use after free in WebRTC in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to 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.