Google Chrome: Use after free in WebUI allows code execution in sandbox
Summary
A use-after-free flaw in the WebUI component of Google Chrome desktop allows a remote attacker to execute arbitrary code inside the browser sandbox. The attacker needs a victim to open a crafted HTML page, for example through a phishing link or a malicious advertisement. The CVE record rates the issue High (CVSS 8.8) and describes code execution inside the sandbox only, without a sandbox escape.
Affected
- Google Chrome desktop versions before 156.0.8078.47 (per the CVE description)
- Unverified: some third-party sources list Windows and macOS builds as 156.0.8078.48
- Chromium-based browsers and Linux distribution packages may be affected; check their vendor advisories
Fixed in
- Google Chrome 156.0.8078.47 or later (per the CVE description and the Chrome Releases post)
- Newer Stable builds exist (third-party pages list 156.0.8078.79/.80); deploy the latest Stable build
- Microsoft Edge and Linux packages: use the fix versions in the respective vendor advisories
Workaround
No workaround known. Apply the security update.
Exploitation
- No evidence of active exploitation found in the sources reviewed
- No public proof of concept found
- CISA KEV status not verified directly
Our recommendation
- Check the installed Chrome version on all endpoints and update to the latest Stable build
- Verify that Edge, Chromium and Linux Chromium packages are updated through their own channels
- Remind users not to open untrusted links and to be cautious with unknown web pages
- Monitor the CISA KEV catalogue and Google's Chrome Releases blog for changes in exploitation status
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
- Microsoft Security Update Guide: CVE-2026-113058 msrc.microsoft.com
- Ubuntu security: CVE-2026-113058 ubuntu.com
- Vulners: CVELIST CVE-2026-113058 vulners.com
- Chrome for Testing (Stable builds) googlechromelabs.github.io
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, 14:28.
Original description (NVD)
Use after free in WebUI 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.