Google Chrome: Improper input validation in PerformanceAPIs
Summary
Google Chrome before 156.0.8078.47 contains an improper input validation flaw in PerformanceAPIs. According to the CVE record, a remote attacker can use a crafted HTML page to potentially execute arbitrary code inside the browser sandbox. The victim must visit the malicious page, so drive-by browsing and malicious links are the main risk. The Chromium bug tracker entry describes a different issue (an information disclosure), so the real impact is uncertain.
Affected
- Google Chrome prior to 156.0.8078.47 (CVE record)
- Microsoft Edge prior to 156.0.4314.42 (HKCERT)
- Chromium-based browsers and Linux distribution packages may be affected; per-release status varies
- Android Chrome: likely affected, not verified
Fixed in
- Google Chrome 156.0.8078.47 or later (Linux)
- Google Chrome 156.0.8078.47/.48 or later (Windows and macOS, per secondary sources)
- Microsoft Edge 156.0.4314.42 or later
- Vendor advisory not opened directly; version details come from secondary coverage
Workaround
- No workaround documented. Update the browser.
- Restart the browser after updating, because the old process may still be running.
Exploitation
- In the wild: no known exploitation (release-level statement, not CVE-specific)
- CISA KEV: not listed according to one aggregator; verify against the KEV catalogue
- Public proof of concept: none found
- CISA SSVC: exploitation none, automatable no, technical impact total
Our recommendation
- Update Google Chrome to 156.0.8078.47 or later, and Microsoft Edge to 156.0.4314.42 or later, on all desktops.
- Restart the browsers after the update.
- Refresh the Chromium snap on Ubuntu and check Linux distribution packages.
- Check whether the Chrome 156 release, which contains 353 fixes, is deployed across the company.
- Monitor the Google bug tracker for clarification of the impact.
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 511311494 issues.chromium.org
- NVD record via Vulners vulners.com
- HKCERT security bulletin (Microsoft Edge) www.hkcert.org
- Ubuntu CVE tracker ubuntu.com
- VulDB entry vuldb.com
- Cybersecurity News: Chrome 156 security update cybersecuritynews.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, 12:18.
Original description (NVD)
Improper input validation 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.