Google Chrome: Integer overflow in Editing allows code execution in sandbox
Summary
Google Chrome before 156.0.8078.79 contains an integer overflow (CWE-190) in its Editing component, which handles rich-text editing. A remote attacker can use a crafted HTML page to potentially execute arbitrary code inside the browser sandbox. The victim must open the malicious page, but no login is required. Full compromise would normally need a further sandbox escape, which the sources do not describe.
Affected
- Google Chrome prior to 156.0.8078.79 (Windows, macOS, Linux)
- Android and iOS builds: Unknown.
Fixed in
- Google Chrome 156.0.8078.79 or later (Stable channel update of 29 October 2026; Windows and macOS 156.0.8078.79/.80, Linux 156.0.8078.79)
- Android and iOS fixed versions: Unknown.
Workaround
- No vendor-published workaround.
- Until patched: confirm the Chrome version on every endpoint, enforce updates via policy or MDM, and restrict browsing to trusted sites on systems that cannot be updated yet.
Exploitation
- No known exploitation as of 30 October 2026 according to the reviewed sources.
- Not listed in CISA KEV at the time of review.
- EPSS 0.2 % (10th percentile).
- Public exploit code: unconfirmed; sources conflict.
- CISA SSVC: Exploitation none, Automatable no, Technical Impact total.
Our recommendation
- Update Google Chrome to 156.0.8078.79 or later on all desktop systems now; treat this as a high-priority item for routine patching within days.
- Verify the version on every endpoint, including systems where auto-update is disabled, unmanaged devices and Linux systems not using Google's repository.
- Check Android and iOS release notes separately.
- The same release fixes other vulnerabilities, so one update covers all of them.
- Recheck CISA KEV and exploit databases before closing the ticket; re-rate if exploitation is reported.
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- Chrome Releases: Stable Channel Update for Desktop (29 October 2026) chromereleases.googleblog.com
- Chromium issue tracker entry issues.chromium.org
- ThreatInt CVE record CVE-2026-119268 cve.threatint.com
- VulDB CVE-2026-119268 vuldb.com
- OffSeq Radar CVE-2026-119268 radar.offseq.com
- Strix CVE-2026-119268 www.strix.ai
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, 08:55.
Original description (NVD)
Integer overflow in Editing in Google Chrome prior to 156.0.8078.79 allowed a remote attacker to potentially 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.