Google Chrome: Use-after-free in Input allows sandboxed code execution
Summary
A use-after-free flaw in the Input component of Google Chrome allows a remote attacker to execute arbitrary code inside the browser sandbox. The attacker needs a user to visit a crafted HTML page. Chromium rates the bug with security severity Low, and CISA SSVC lists technical impact as total.
Affected
- Google Chrome prior to 156.0.8078.47 (per NVD)
- Chromium-based products that consume the affected Chromium code until they ship the fix (for example Microsoft Edge; fixed build unknown)
- Linux distributions package Chromium separately; check the vendor advisory for each package
Fixed in
- Google Chrome 156.0.8078.47 or later (per NVD). Vendor build numbers differ by platform; Windows and macOS builds may be 156.0.8078.48 or higher.
- Newer builds (for example 156.0.8078.79 or .80) are reported by secondary sources and should be verified on the Chrome Releases blog.
- Fixed Microsoft Edge build: Unknown.
- Linux distributions: Debian and FreeBSD have published Chromium updates; fixed package versions were not confirmed.
Workaround
- No workaround is documented in the sources. Updating Chrome is the only known remedy.
Exploitation
- No evidence of exploitation in the wild was found. The GitHub alert reviewed lists the CVE as not in CISA KEV and EPSS as unknown.
- No public proof of concept was found in the sources reviewed.
Our recommendation
- Update Google Chrome to the newest stable build on all Windows, macOS and Linux systems, and update Chromium-based browsers such as Edge once fixed builds are published.
- Enforce a minimum Chrome version with your management tool and verify compliance.
- Chrome applies updates on relaunch, so ask users to restart the browser after an update is downloaded.
- Ubuntu users should update the Chromium snap rather than the chromium-browser deb package.
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- Chrome Releases: Stable Channel Update for Desktop, 20 Oct 2026 chromereleases.googleblog.com
- Chromium issue tracker 533113044 issues.chromium.org
- Microsoft MSRC update guide entry msrc.microsoft.com
- Ubuntu security tracker ubuntu.com
- Vulners CVE listing vulners.com
- GitHub alert (exploitation status) github.com
- Wikipedia: Google Chrome en.wikipedia.org
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, 14:51.
Original description (NVD)
Use after free in Input in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Low)
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.