Google Chrome: Memory corruption in Frames allows code execution in sandbox
Summary
A memory corruption flaw (CWE-119) in the Frames component of desktop Google Chrome allows a remote attacker to potentially execute arbitrary code inside the browser sandbox. Exploitation requires the victim to open a crafted HTML page, so user interaction is needed but no authentication. The CVSS 3.1 base score is 8.8 (High).
Affected
- Google Chrome desktop prior to 156.0.8078.47
- Per third-party summaries of the release notes, Windows and macOS builds may be affected up to 156.0.8078.48; not confirmed on Google's page
- Android Chrome builds prior to 156.0.8078.47 (per third-party summaries, unconfirmed)
- Chromium-based browsers that ingest this fix (e.g. Microsoft Edge) are also affected until they are updated
Fixed in
- Google Chrome 156.0.8078.47 (Linux)
- Google Chrome 156.0.8078.47 or 156.0.8078.48 depending on rollout (Windows and macOS, to be confirmed on Google's Chrome Releases post)
- Edge and other Chromium-based browsers: vendor-specific fixed builds, check the vendor advisory
Workaround
- No vendor-specific workaround is known. Apply the update.
- Restart the browser after updating, as the fix only takes effect after a restart.
Exploitation
- Exploited in the wild: no evidence found in the sources reviewed; not verified against CISA KEV or Google's release notes.
- Public proof of concept: none found.
- CISA SSVC assessment: exploitation none, not automatable, technical impact total.
Our recommendation
- Update Google Chrome to 156.0.8078.47 or later (156.0.8078.48 on Windows and macOS if rollout requires it) and restart the browser.
- Update other Chromium-based browsers and check Linux packages (Chromium snap or distribution package) for their fixed versions.
- Check the installed version on all desktops, including those that are not centrally managed.
- Monitor for unusual browser crashes or behaviour and keep the browser auto-update enabled.
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-113104 msrc.microsoft.com
- Ubuntu security: CVE-2026-113104 ubuntu.com
- Vulners CVE record: CVE-2026-113104 vulners.com
- Cybersecurity News: Chrome security update fixing 353 flaws cybersecuritynews.com
- Windows Forum: Chrome 156 security update windowsforum.com
- HKCERT security bulletin: 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, 13:58.
Original description (NVD)
Memory corruption in Frames 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: High)
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.