Google Chrome: Use-after-free in Media allows code execution in sandbox
Summary
A use-after-free flaw in the Media component of Google Chrome before 156.0.8078.47 can be triggered by a crafted HTML page. An attacker who lures a user to such a page can execute arbitrary code inside the browser sandbox. NVD rates the issue 8.8 (High), while Google's Chromium severity is Low and the description limits the impact to the sandbox. No exploitation in the wild or public proof of concept was found at the time of research.
Affected
- Google Chrome (desktop: Windows, macOS, Linux) prior to 156.0.8078.47 per NVD
- Chromium-based products that include this fix, such as Microsoft Edge and Linux distribution Chromium packages, are also affected until they are updated (versions unverified)
Fixed in
- Google Chrome 156.0.8078.47 or later (Linux, per Wikipedia; Windows and macOS build 156.0.8078.48 per Wikipedia, not verified against Google's advisory)
- Newer stable builds exist; use the current Chrome 156 stable build or later
- Debian and Ubuntu: fixed package versions unknown; check the distribution security trackers
- Microsoft Edge: a HKCERT bulletin lists 156.0.4314.42, not confirmed against MSRC
Workaround
- No vendor workaround known. Applying the update is the mitigation.
Exploitation
- In the wild: No evidence found; CISA KEV status not directly verified.
- Public proof of concept: None found.
- CISA SSVC: Exploitation none, Automatable no, Technical impact total.
- VulDB broker price estimate USD 5k to 25k (not evidence of exploitation).
Our recommendation
- Update all Chrome, Chromium and Edge installations to Chrome 156 stable or later, enforced via policy (for example MDM or Chrome Browser Cloud Management).
- Verify the browser version on each endpoint after the update.
- Update Chromium packages on Linux systems through the distribution (Ubuntu: snap refresh).
- Treat as high priority because the flaw is remotely triggerable through normal browsing and Chrome is widely deployed.
- Monitor for updates to the Chromium issue tracker and CISA KEV.
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- Google Chrome Releases: Stable Channel Update for Desktop chromereleases.googleblog.com
- Chromium issue tracker issues.chromium.org
- VulDB entry 424645 vuldb.com
- Ubuntu security tracker CVE-2026-113314 ubuntu.com
- Vulners CVELIST:CVE-2026-113314 vulners.com
- HKCERT security bulletin Microsoft Edge www.hkcert.org
- Google Chrome (Wikipedia) en.wikipedia.org
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, 12:03.
Original description (NVD)
Use after free in Media 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: Low)
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.