Google Chrome: Use-after-free in PerformanceAPIs allows code execution
Summary
Google Chrome before 156.0.8078.47 contains a use-after-free vulnerability in the PerformanceAPIs component. A remote attacker can use a crafted HTML page to potentially execute arbitrary code outside the browser sandbox. The attack requires that a user visits the page, but no authentication. Google rates the issue Medium, while the CVSS score is 9.6 (Critical).
Affected
- Google Chrome prior to 156.0.8078.47
- Chromium-based browsers and embedded builds that include the affected Chromium code, depending on their update timing
- Ubuntu chromium-browser package: listed as not affected (wrapper around Snap); check the Chrome deb or Snap build instead
Fixed in
- Google Chrome 156.0.8078.47 or later on all platforms (Windows and Mac build .47 or .48 unconfirmed)
- Newer desktop update of 27 October 2026: 156.0.8078.73/.74 (Windows/Mac) and .73 (Linux); deploy the newest stable build
- Debian DSA 6577-1 and DLA 4853-1 for chromium (fixed package versions not verified)
Workaround
Unknown. No vendor workaround found; updating is the remedy.
Exploitation
- No evidence of in-the-wild exploitation found
- No public proof-of-concept found
- Not verified against the CISA KEV catalog
Our recommendation
- Update Google Chrome to the newest stable build on all workstations and restart the browser, as staged updates may keep the old process running
- Enforce browser updates via group policy or MDM and check the version on managed and unmanaged devices
- Check other Chromium-based browsers and embedded builds for updates
- Monitor the CISA KEV catalog 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
- Microsoft Security Update Guide: CVE-2026-113014 msrc.microsoft.com
- Ubuntu CVE tracker: CVE-2026-113014 ubuntu.com
- Vulners: CVE-2026-113014 vulners.com
- Browserhow: Chrome 156 stable update browserhow.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 30 Oct 2026, 22:41.
Original description (NVD)
Use after free in PerformanceAPIs in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially execute arbitrary code outside 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.