Google Chrome: Memory corruption in Chromoting allows sandbox code execution
Summary
A memory corruption flaw (CWE-119) in the Chromoting component of Google Chrome before 156.0.8078.47 can be triggered by a crafted HTML page. A remote attacker could potentially execute arbitrary code inside the browser sandbox. The attack requires a user to open the malicious page, but no authentication. Full system compromise would normally need a second flaw to escape the sandbox.
Affected
- Google Chrome (desktop) prior to 156.0.8078.47, per the CVE description
- The official CVE record lists the range as 156.0.8078.47 to < 156.0.8078.47, which conflicts with the description. Unknown which range is correct.
- Microsoft Edge (Chromium-based) is covered by a separate advisory and is not confirmed here.
Fixed in
- Linux: 156.0.8078.47 (vendor release notes, reported by secondary sources)
- Windows and macOS: 156.0.8078.47/.48 (reported by secondary sources)
- Later stable build: 156.0.8078.73/.74 for Windows and macOS, 156.0.8078.73 for Linux (Malwarebytes)
Workaround
- None needed where patching is possible.
- Restart the browser after updating so the fix takes effect.
- If Chrome Remote Desktop is not used, consider removing it to reduce the attack surface (own recommendation, not from a source).
Exploitation
- No known exploitation in the wild. Strix lists the CVE as not in CISA's KEV catalogue.
- No public proof of concept found. The Chromium issue tracker entry was not accessible, so restricted details cannot be ruled out.
- CISA SSVC assessment: Exploitation none, Automatable no, Technical Impact total.
Our recommendation
- Update Chrome on all desktop systems to the latest stable build, not only 156.0.8078.47.
- Confirm the installed version on endpoints and restart browsers that have not restarted since the update.
- Push updates centrally where possible and check Edge and Linux Chromium packages separately.
- Priority: medium to high for browser fleets, because phishing and malicious links are the likely delivery route.
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
- Strix: CVE-2026-113258 www.strix.ai
- VulDB: vuln 424515 vuldb.com
- Malwarebytes: Chrome and Firefox updates fix serious security flaws www.malwarebytes.com
- GBHackers: Google Chrome 156 fixes 353 security vulnerabilities gbhackers.com
- Cybersecurity News: Chrome security update fixing 353 flaws cybersecuritynews.com
- HKCERT: Microsoft Edge multiple vulnerabilities www.hkcert.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:34.
Original description (NVD)
Memory corruption in Chromoting 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.