Google Chrome: Memory corruption in Media allows code execution in sandbox
Summary
A memory corruption flaw in the Media component of Google Chrome allows a remote attacker to potentially execute arbitrary code inside the browser sandbox. Exploitation requires that a user opens a crafted HTML page, for example via an email link or a website. Chromium rates the issue Medium, and the public information does not describe a sandbox escape.
Affected
- Google Chrome desktop before 156.0.8078.47 on Linux
- Google Chrome desktop before 156.0.8078.47/.48 on Windows and macOS
- Android builds: 156.0.8078.47 is listed as the fixed version by secondary sources (affected range not confirmed by the vendor)
- The official CVE record gives an inconsistent affected range (156.0.8078.47 to < 156.0.8078.47); the vendor advisory should be checked.
Fixed in
- Linux and Android: 156.0.8078.47
- Windows and macOS: 156.0.8078.47/.48
- Source: Chrome Releases, Stable Channel Update for Desktop, 20 October 2026 (version data taken from secondary reports; verify against the vendor advisory)
Workaround
- No vendor-documented workaround. Apply the update.
- Fully restart the browser after updating, as an old browser process may still run.
Exploitation
- No known exploitation at release (secondary source; Google often does not disclose this at release).
- CISA SSVC assessment in the CVE record: Exploitation none, Automatable no, Technical Impact total.
- No public proof of concept found.
Our recommendation
- Update Google Chrome on all endpoints to the fixed versions, prioritising Windows and macOS systems and those with unmanaged updates.
- Restart the browser and verify the installed version on each endpoint, for example via fleet management or Chrome policy tooling.
- Install the update together with the other fixes in Chrome 156, which contains 353 security fixes in total.
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 entry issues.chromium.org
- NVD mirror (Vulners): CVE-2026-113257 vulners.com
- HKCERT security bulletin: Google Chrome multiple vulnerabilities www.hkcert.org
- Cybersecuritynews: Chrome security update fixing 353 flaws cybersecuritynews.com
- Ubuntu security: CVE-2026-113257 ubuntu.com
- Windowsforum: Chrome 156 security update windowsforum.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, 12:33.
Original description (NVD)
Memory corruption in Media in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
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.