Google Chrome: Memory corruption in ContentCapture allows sandboxed code execution
Summary
Memory corruption in the ContentCapture component of Google Chrome on Android allows a remote attacker to execute arbitrary code inside the browser sandbox. The attacker needs the victim to open a crafted HTML page, for example via a phishing link or a malicious website. The CVSS score is 8.8 (High), while Chromium rates the issue Low; a sandbox escape would be required for full device compromise.
Affected
- Google Chrome for Android prior to 156.0.8078.47
- Range in some third-party databases is malformed; the intended meaning is 'before 156.0.8078.47'
- Microsoft Edge (Chromium-based) prior to 156.0.4314.42 is listed as affected by Microsoft and HKCERT
- Ubuntu lists its chromium-browser packages as Not affected
Fixed in
- Google Chrome for Android 156.0.8078.47 (per secondary reports; not confirmed directly in Google's post)
- Microsoft Edge 156.0.4314.42 or later (per HKCERT)
Workaround
No workaround documented. Apply the update.
Exploitation
- No evidence of active exploitation found; not listed in CISA KEV at the time of research
- No public proof-of-concept found
- Google's notices do not always state exploitation status; check the Chrome Releases post and CISA KEV for updates
Our recommendation
- Verify that all Android devices with Chrome run version 156.0.8078.47 or later
- Enable Google Play auto-updates or enforce the update via MDM, with priority for BYOD and mobile staff devices
- Remind users to avoid opening links from untrusted sources
- Monitor the Google advisory and CISA KEV for changes in exploitation status
- Check the Chromium bug tracker entry once it is public
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
- Vulners CVE record vulners.com
- HKCERT security bulletin (Microsoft Edge) www.hkcert.org
- Ubuntu CVE tracker ubuntu.com
- VulDB entry vuldb.com
- GBHackers: Chrome 156 fixes 353 vulnerabilities gbhackers.com
- Strix CVE record www.strix.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:20.
Original description (NVD)
Memory corruption in ContentCapture in Google Chrome on on Android 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.