Google Chrome: Use-after-free in Track allows code execution in sandbox
Summary
Google Chrome versions before 155.0.8059.39 contain a use-after-free vulnerability in the component named Track. A remote attacker can execute arbitrary code inside the browser sandbox by luring a user to a crafted HTML page. The attack requires that the user opens the page, for example during ordinary web browsing. The Chromium security severity is rated Critical, but no sandbox escape has been reported.
Affected
- Google Chrome prior to 155.0.8059.39 (Linux)
- Google Chrome prior to 155.0.8059.39/.40 (Windows and Mac)
- Downstream Chromium packages of Linux distributions and Chromium-based browsers (versions vary, see vendor pages)
Fixed in
- Google Chrome 155.0.8059.39 or later for Linux
- Google Chrome 155.0.8059.39/.40 or later for Windows and Mac
- Preferably the current Stable release of Chrome
- Edge and other Chromium-based browsers: use the vendor's release notes, as version data conflicts between sources
Workaround
Unknown. No vendor-published workaround was found; the fix is the update.
Exploitation
- CISA SSVC: Exploitation none, Automatable no, Technical Impact total
- Not listed as known exploited by the sources checked (CISA KEV not directly verified)
- No public proof of concept found; this is not confirmed absent
- Google's announcement does not describe specific exploitation methods
Our recommendation
- Update Google Chrome to at least 155.0.8059.39 (Linux) or 155.0.8059.39/.40 (Windows/Mac), preferably the current Stable release
- Check the version on all endpoints, especially where auto-updates are managed or disabled
- Update Edge, other Chromium-based browsers and Linux chromium packages separately
- Prioritise workstations with local admin rights and browsers used on the open web
- Monitor for public exploit reports and CISA KEV entries
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
- CIS Advisory: Multiple vulnerabilities in Google Chrome www.cisecurity.org
- Malwarebytes: Update Chrome and ChromeOS to fix critical security issues www.malwarebytes.com
- SecurityWeek: Chrome 155 update patches 247 vulnerabilities www.securityweek.com
- Vulners: CVE-2026-106347 (MS) vulners.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, 21:51.
Original description (NVD)
Use after free in Track in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Critical)
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.