Google Chrome: Memory corruption in ServiceWorker
Summary
A memory corruption flaw in the ServiceWorker component of Google Chrome allows a remote attacker to potentially execute arbitrary code inside the browser sandbox. The attack requires a user to open a crafted HTML page. Chromium rates the issue Medium and NVD scores it 8.8 (High). A sandbox escape would be needed for full system compromise, and the sources report no known exploitation.
Affected
- Google Chrome desktop builds prior to 156.0.8078.47 (per NVD/CNA description)
- The CNA record's affected range is internally inconsistent ("156.0.8078.47 to < 156.0.8078.47"), so verify the exact range against the vendor post.
Fixed in
- Google Chrome 156.0.8078.47 or later (per NVD description)
- Secondary reports list 156.0.8078.47/.48 for Windows and macOS and 156.0.8078.47 for Linux and Android. These are not confirmed by the vendor post, which could not be reviewed.
Workaround
Unknown. No mitigation is documented beyond applying the update.
Exploitation
- No known active exploitation in the sources reviewed.
- Not listed in CISA KEV according to one aggregator.
- No public proof of concept or exploit code found.
Our recommendation
- Update Chrome to 156.0.8078.47 or later on all endpoints and restart the browser.
- Verify the installed version on each machine, as the desktop rollout is gradual.
- Check other Chromium-based browsers in use (e.g. Edge, Brave) and their vendor advisories.
- Check Ubuntu snap and Debian Chromium packages separately, as their status is unclear.
- Re-check NVD and CISA KEV if exploitation is reported.
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-113172 msrc.microsoft.com
- Ubuntu CVE tracker: CVE-2026-113172 ubuntu.com
- NVD mirror via Vulners: CVE-2026-113172 vulners.com
- VulDB: CVE-2026-113172 vuldb.com
- Security notice: Google Chrome 156 stable www.techgeeks.org
- Chrome 156 security update analysis (Windows Forum) 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:25.
Original description (NVD)
Memory corruption in ServiceWorker 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.