Google Chrome: Memory corruption in DataTransfer
Summary
Memory corruption in the DataTransfer component of Google Chrome before 156.0.8078.47 can be triggered by a crafted HTML page. An attacker may be able to execute arbitrary code inside the browser sandbox. The attack requires that a user visits the malicious page, and the sandbox limits the impact, so a further vulnerability would normally be needed for full system compromise. The CNA rates the issue 8.8 (High), while Google rates it Medium.
Affected
- Google Chrome prior to 156.0.8078.47 (desktop, per the CVE description)
- Note: the official CVE record lists the range as '156.0.8078.47 to < 156.0.8078.47', which is inconsistent. Verify against the vendor advisory.
- Microsoft Edge (Chromium-based) may also be affected, as it uses the same Chromium code. Unknown.
Fixed in
- Linux: 156.0.8078.47
- Android: 156.0.8078.47
- Windows and macOS: 156.0.8078.47 or 156.0.8078.48
- iOS: Unknown. Sources disagree on the build number (156.0.8078.46 or 156.0.8078.54). Check Apple and Google.
Workaround
- No workaround is needed, because a patch exists.
- Restart the browser after updating, because the fix only takes effect in a new process.
Exploitation
- Exploited in the wild: none reported. CISA SSVC assessment: Exploitation none, Automatable no.
- Public proof-of-concept: none found in the sources reviewed.
Our recommendation
- Update Chrome to 156.0.8078.47 or later on Linux and Android, and to 156.0.8078.47/.48 or later on Windows and macOS, as a priority.
- Check the browser version on all managed endpoints (for example with Chrome Enterprise or Intune) and confirm that the browser was restarted.
- Patch the whole Chrome 156 release, not only this CVE, because the release fixes 353 security issues.
- Inform users not to open untrusted links or HTML pages while the update is pending.
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-113124 msrc.microsoft.com
- Ubuntu CVE tracker: CVE-2026-113124 ubuntu.com
- VulDB: vuln 424294 vuldb.com
- Vulners: CVELIST CVE-2026-113124 vulners.com
- Cybersecurity News: Chrome security update fixing 353 flaws cybersecuritynews.com
- GBHackers: Google Chrome 156 fixes 353 security vulnerabilities gbhackers.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, 13:51.
Original description (NVD)
Memory corruption in DataTransfer 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.