Google Chrome: Memory corruption in PerformanceAPIs allows code execution in sandbox
Summary
A memory corruption flaw in the PerformanceAPIs component of Google Chrome before 156.0.8078.47 may allow a remote attacker to execute code inside the renderer sandbox. Exploitation requires the victim to open a crafted HTML page, typically through a malicious or compromised website or a phishing link. Full compromise would normally also require a second sandbox-escape flaw; this is an assessment, not a vendor statement. The NVD CVSS score is 8.8 (High), and Chromium rates the issue Medium.
Affected
- Google Chrome (desktop) prior to 156.0.8078.47 per the CVE record
- Downstream Chromium-based products that ingest the fix, such as Microsoft Edge (Chromium-based)
Fixed in
- Google Chrome 156.0.8078.47 or later (minimum fixed build per CVE record and third-party trackers)
- Later stable builds exist (reported as 156.0.8078.79/.80 for Windows and macOS, 156.0.8078.79 for Linux); install the latest stable build
- Build numbers differ between sources for macOS/Windows; verify on the vendor advisory
Workaround
No workaround needed. A patch is available. Chrome updates automatically after a relaunch; check manually via Menu > Help > About Google Chrome.
Exploitation
- No evidence of exploitation in the wild found in the research notes; verify against the CISA KEV catalogue.
- No public proof of concept found; this is absence of evidence, not confirmed absence.
- CISA SSVC assessment: exploitation PoC, not automatable, total technical impact.
Our recommendation
- Update Google Chrome and Chromium-based browsers such as Microsoft Edge to the latest stable build within days.
- Managed fleets: push the current stable build via MDM or policy tooling and verify the version.
- Check Ubuntu hosts for the Chromium snap version, since the chromium-browser package is a wrapper.
- Raise the priority if users browse untrusted content or handle sensitive data.
- Verify the NVD record and the Chromium bug 511325076.
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 511325076 issues.chromium.org
- HKCERT security bulletin on Google Chrome www.hkcert.org
- OSV: Chainguard advisory CGA-h5qf-8hf9-6vcf osv.dev
- Ubuntu security tracker CVE-2026-113146 ubuntu.com
- Vulners: CVE-2026-113146 (CVE list) vulners.com
- TechSpot: Google Chrome download www.techspot.com
- VulDB: sibling CVE-2026-113056 (for differentiation) vuldb.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:41.
Original description (NVD)
Memory corruption in PerformanceAPIs 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.