Google Chrome: Memory corruption in FullScreen allows sandbox code execution
Summary
Google Chrome for desktop contains a memory corruption flaw in its FullScreen component (CVE-2026-113149). A remote attacker can use a crafted HTML page to execute arbitrary code inside the browser sandbox. The attack requires a user to open the attacker's page, but no authentication is needed. The Chromium bug tracker describes the underlying issue as fullscreen being granted while a tab-modal dialog is shown, which could enable UI spoofing; the official classification remains memory corruption.
Affected
- Google Chrome desktop builds before 156.0.8078.47
- Windows and macOS: some sources list 156.0.8078.48 as the fixed build, so treat builds before 156.0.8078.48 as affected there
- Android builds before 156.0.8078.47 are also listed by a third-party source
Fixed in
- Google Chrome 156.0.8078.47 or later (Linux)
- Google Chrome 156.0.8078.48 or later (Windows and macOS; verify against the vendor advisory)
Workaround
Unknown. No workaround is documented in the sources. Apply the update.
Exploitation
- In the wild: No evidence found. A CISA KEV listing could not be confirmed.
- Public proof of concept: None found.
- CISA SSVC assessment: Exploitation none, automatable no, technical impact total.
Our recommendation
- Update Chrome on all desktops to 156.0.8078.48 or later (Windows and macOS) or 156.0.8078.47 or later (Linux) as soon as possible.
- Restart the browser after the update so the new version takes effect.
- Verify the installed version on each endpoint, including managed devices, instead of relying on the update prompt.
- Check Microsoft Edge and other Chromium-based browsers separately against the MSRC entry, and check Debian and Ubuntu Chromium packages.
- Apply the whole Chrome 156 release, as it fixes 353 further security issues.
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 517221283 issues.chromium.org
- Microsoft MSRC Security Update Guide entry msrc.microsoft.com
- Ubuntu security notice CVE-2026-113149 ubuntu.com
- Vulners NVD record CVE-2026-113149 vulners.com
- Strix CVE record CVE-2026-113149 www.strix.ai
- GBHackers: Chrome 156 fixes 353 security vulnerabilities gbhackers.com
- Windows Forum: 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, 13:34.
Original description (NVD)
Memory corruption in FullScreen in Google Chrome 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: 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.