Google Chrome: Use after free in Paint allows sandboxed code execution
Summary
Google Chrome versions prior to 156.0.8078.73 contain a use-after-free flaw in the Paint component. A remote attacker can execute arbitrary code inside the browser sandbox by luring a user to a crafted HTML page. The attack needs no authentication but requires user interaction, such as visiting the page. The description does not mention a sandbox escape, so full system compromise would normally require an additional vulnerability.
Affected
- Google Chrome (desktop) prior to 156.0.8078.73
- Affected range per CVE record: 156.0.8078.73 to < 156.0.8078.73 (as listed by the CNA; the boundary is unclear)
Fixed in
- Google Chrome 156.0.8078.73 or later (per the Stable Channel Update of 27 October 2026; Windows and Mac builds reported as 156.0.8078.73/.74 in secondary sources, not yet verified against the vendor post)
- Linux: google-chrome-stable 156.0.8078.73-1 (Ubuntu package listing)
- Chromium on Ubuntu (snap wrapper) is marked not affected; this does not cover Google Chrome
Workaround
- No vendor-documented workaround is known. Updating is the fix.
- Enforce a minimum Chrome version through the managed update policy.
Exploitation
- No evidence of in-the-wild exploitation found.
- Not listed in CISA KEV according to a third-party snapshot; verify directly with CISA.
- No public proof-of-concept code found.
- CISA SSVC: Exploitation none, Automatable no, Technical Impact total.
- EPSS: 0.26 % (percentile 18).
Our recommendation
- Check the Chrome version on all endpoints and servers; target 156.0.8078.73 or later.
- Force the update through managed policy and restart browsers.
- Apply the Stable Channel Update as a bundle, since it fixes 52 vulnerabilities in total.
- Patch within your emergency or high-priority window, as the browser is internet-facing.
- Re-check the Google advisory and CISA KEV after one to two weeks for changes in exploitation status.
- Check the update status of derivative browsers (for example Brave, Vivaldi, Edge) through their own advisories.
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 entry issues.chromium.org
- Ubuntu CVE tracker ubuntu.com
- OffSeq Radar threat entry radar.offseq.com
- Ubuntu Updates: google-chrome-stable www.ubuntuupdates.org
- Cybersecurity News: Google fixes 52 Chrome security flaws 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, 09:45.
Original description (NVD)
Use after free in Paint in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
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.