Google Chrome: Use after free in Editing component
Summary
A use-after-free vulnerability in the Editing component of Google Chrome allows a remote attacker to execute arbitrary code inside the browser sandbox. Exploitation requires that a victim opens a crafted HTML page, for example via a phishing link or a malicious website. Chromium rates the issue Low, and no exploitation in the wild or public proof of concept has been reported.
Affected
- Google Chrome prior to 156.0.8078.47 (desktop)
- Microsoft Edge (Chromium-based) is also affected according to a third-party advisory; verify against MSRC
- Ubuntu chromium-browser package: not affected (Ubuntu ships Chromium as a snap, which is not covered by this statement)
Fixed in
- Google Chrome 156.0.8078.47 or later (Stable Channel Update for Desktop, 20 October 2026)
- Current desktop builds: Windows and macOS 156.0.8078.48; Linux 156.0.8078.47
- Later 156 builds also cover this CVE; confirm the exact build against the vendor advisory
- Microsoft Edge: 156.0.4314.42 or later according to a third-party advisory (unverified)
Workaround
- Unknown. No vendor workaround documented; patching is the remedy.
- Enforce browser restarts after updates and verify the build version across the fleet, for example via managed Chrome update policies.
Exploitation
- No evidence of exploitation in the wild; no CISA KEV entry known.
- No public proof of concept found.
- CISA SSVC: exploitation none, automatable no, technical impact total.
- EPSS score 0.00406 (low predicted exploitation probability).
Our recommendation
- Update all Google Chrome and Microsoft Edge installations to Chrome 156.0.8078.47 or later (preferably the latest 156 build).
- Make sure browsers are restarted after the update, since the new version only takes effect after relaunch.
- Verify the installed version across all workstations, for example via managed update policies or inventory tools.
- Prioritise workstations with regular web browsing; keep web filtering and phishing protection active.
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
- Microsoft MSRC update guide msrc.microsoft.com
- Ubuntu security tracker ubuntu.com
- HKCERT security bulletin (Microsoft Edge) www.hkcert.org
- Vulners CVE record vulners.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:55.
Original description (NVD)
Use after free in Editing 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.