Google Chrome: Memory corruption in Scheduling allows sandbox code execution
Summary
Google Chrome prior to 156.0.8078.47 contains a memory corruption flaw in its Scheduling component. A remote attacker can use a crafted HTML page to potentially execute arbitrary code inside the browser sandbox. The attack requires the user to open the malicious page, for example through a link or a compromised website.
Affected
- Google Chrome prior to 156.0.8078.47 (per CVE description)
- Vendor-stated range per the CVE record: 156.0.8078.47 to < 156.0.8078.47
- Other third-party sources list a different range (up to 155.0.8059.84); use the vendor range as authoritative
Fixed in
- Google Chrome 156.0.8078.47 or later (Linux, Windows, Mac per HKCERT)
- Recommended target: a later stable build such as 156.0.8078.73 or newer, which also includes this fix (not confirmed as listed for this CVE)
- Chromium-based products such as Microsoft Edge and Linux distribution Chromium packages also receive fixes
Workaround
- Unknown. No workaround is documented in the sources reviewed.
- Patching is the practical mitigation.
Exploitation
- Exploited in the wild: No evidence found. The Strix aggregator lists KEV: No; CISA KEV was not checked directly.
- Public proof of concept: None found.
- CISA SSVC: Exploitation none, Automatable no, Technical Impact total.
- VulDB lists the status as 0-Day; this is not explained and is not evidence of exploitation.
Our recommendation
- Update Google Chrome to 156.0.8078.47 or later, preferably the newest stable build, across all endpoints.
- Check the browser version on all managed devices, especially where auto-update is blocked or browsers are rarely restarted.
- Relaunch the browser after updating so the new version takes effect.
- Prioritise machines that browse untrusted web content.
- Apply the same update to Chromium-based browsers such as Microsoft Edge.
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- CVE description and NVD data vulners.com
- Chrome Releases: Stable Channel Update for Desktop (cited by CVE) chromereleases.googleblog.com
- Chromium issue tracker issues.chromium.org
- HKCERT security bulletin www.hkcert.org
- VulDB entry vuldb.com
- Strix CVE record www.strix.ai
- Debian/Chromium CVE listing vulners.com
- Betanews: Chrome and Firefox security patches betanews.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:11.
Original description (NVD)
Memory corruption in Scheduling 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: 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.