Google Chrome: Memory corruption in HTML processing
Summary
Google Chrome before 156.0.8078.47 contains a memory corruption flaw in HTML processing. A remote attacker can use a crafted HTML page to potentially execute arbitrary code inside the browser sandbox. The victim only needs to open the malicious page, and no login is required. Google rates the severity as Low, while the CVSS base score is 8.8.
Affected
- Google Chrome prior to 156.0.8078.47 (desktop)
- Chromium-based browsers, such as Microsoft Edge, depending on the Chromium version they include
Fixed in
- Google Chrome 156.0.8078.47 or later (minimum build on all platforms; check the vendor page for the exact build per platform)
- Debian: DSA 6577-1 and DLA 4853-1 (Chromium)
- Ubuntu: the fix is delivered via the Snap package, not the .deb package chromium-browser
- Microsoft Edge: fixed build unknown
Workaround
- No workaround documented. Update the browser.
- Restart the browser after updating, because an old process may still run after the update prompt.
Exploitation
- No evidence of exploitation in the wild found.
- Not listed in the CISA KEV catalog according to the tracker entry.
- No public proof of concept found.
Our recommendation
- Inventory Chrome, Chromium and Edge versions on all endpoints; the minimum target is 156.0.8078.47.
- Confirm the update is installed and the browser has been restarted.
- Apply distribution updates on Linux systems (Debian DSA/DLA, FreeBSD) and check the Snap channel on Ubuntu.
- Prioritise managed fleets, since web browsing and mail links are the realistic attack path.
- Recheck NVD and the Chrome release page for changes.
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
- NVD record via Vulners vulners.com
- Ubuntu security tracker ubuntu.com
- Microsoft Security Update Guide msrc.microsoft.com
- Windows Forum: Chrome 156 security update windowsforum.com
- Cybersecurity News: Chrome security update cybersecuritynews.com
- CISA KEV status (tracker entry) github.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, 14:46.
Original description (NVD)
Memory corruption in HTML 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.