CVE-2026-119268
published 2026-10-30CVE-2026-119268: 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…
PriorityP351high8.8CVSS 3.1
AVNACLPRNUIRSUCHIHAH
EPSS
0.20%
9.7th percentile
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)
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| chrome | < 156.0.8078.79 | 156.0.8078.79 | |
| chrome | >= 156.0.8078.79 < 156.0.8078.79 | 156.0.8078.79 | |
| chrome_desktop | — | — |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
Google Chrome up to 156.0.8078.73 Editing integer overflow
vuldb·2026-10-30
CVE-2026-119268 [CRITICAL] Google Chrome up to 156.0.8078.73 Editing integer overflow
A vulnerability, which was classified as critical, has been found in Google Chrome. Impacted is an unknown function of the component Editing. The manipulation leads to integer overflow.
This vulnerability is uniquely identified as CVE-2026-119268. The attack is possible to be carried out remotely. No exploit exists.
It is advisable to upgrade the affected component.
Chrome
Stable Channel Update for Desktop: CVE-2026-119267
vendor_chrome·2026-10-29
CVE-2026-119267 [HIGH] Stable Channel Update for Desktop: CVE-2026-119267
Stable Channel Update for Desktop
CVE-2026-119267: Memory corruption in DOM. Reported by Xinyang Ge on 2026-10-21 [N/A][ 576984708 ] High CVE-2026-119268: Integer overflow in Editing
Reported by Xinyang Ge on 2026-10-23 [N/A][ 577072000 ] High CVE-2026-119269: Use after free in Blink
Severity: high
No detection rules found.
No public exploits indexed.
2026-10-30
Published