Google Chrome: Memory corruption in Sensor component
Summary
A memory corruption flaw in the Sensor component of Google Chrome before 156.0.8078.47 can be triggered by a crafted HTML page. A remote attacker could potentially execute arbitrary code inside the browser sandbox. The victim must visit the malicious page, and the Chromium bug report describes a sandbox escape that requires an already compromised renderer.
Affected
- Google Chrome prior to 156.0.8078.47
- Chromium-based products that include the same code, such as Microsoft Edge, may also be affected; check their vendor advisories
Fixed in
- Google Chrome 156.0.8078.47 or later (Windows, macOS, Linux)
- Newer stable builds are available; install the current stable release
Workaround
- Unknown. The vendor advisory lists no interim mitigations.
- Updating Chrome is the fix.
Exploitation
- No known exploitation in the wild at the time of writing.
- No public proof of concept found.
- CISA SSVC: exploitation none, automatable no, technical impact total.
- The Chromium bug report describes concurrent cross-apartment access to a COM sensor object in the legacy Win32 sensor implementation, which can cause heap corruption.
Our recommendation
- Update Google Chrome and any Chromium-based browsers to the latest stable build on all endpoints.
- Check endpoints with a vulnerability scanner for Chrome builds below 156.0.8078.47.
- Prioritise unmanaged Windows systems and endpoints with delayed or pinned browser updates.
- Monitor the vendor release notes and the Chromium bug for changes in exploitation status or platform scope.
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 msrc.microsoft.com
- Ubuntu CVE tracker ubuntu.com
- Vulners CVE list entry vulners.com
- Strix CVE summary 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, 14:31.
Original description (NVD)
Memory corruption in Sensor 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.