Chrome Patches Dozens of RCE Flaws
Google Chrome versions before 154.0.8037.57/.58 contain numerous memory-corruption and other bugs that could allow arbitrary code execution; no in-the-wild exploitation reported yet.
Sourcecisecurity.org — open the original
What to check
- Applies to
- The 40 CVEs named below. Whether you run an affected version is not assessed: check the versions the source lists.
- Exploitation
- No exploitation in the wild and no public exploit is recorded for the CVEs named.
MS-ISAC issued an advisory detailing a large batch of vulnerabilities patched in Google Chrome (prior to 154.0.8037.57/.58 for Windows/Mac and 154.0.8037.57 for Linux). The most severe issues are memory-safety bugs — buffer overflows, use-after-free, out-of-bounds writes, and type confusion — spread across core browser components including ANGLE, GPU, V8, WebGL, PDFium, ServiceWorker, Bluetooth, HID, and DevTools. Successful exploitation of the most severe flaws could allow an attacker to achieve arbitrary code execution in the context of the logged-in user, potentially leading to installation of programs, data manipulation, or creation of new accounts, with impact scaled to the privileges of the affected account.
The advisory also lists numerous lower-severity issues such as missing/incorrect authorization checks, UI misrepresentation (spoofing), information leaks, and confused-deputy conditions across features like Navigation, Extensions, Payments, Passwords, and Safebrowsing. These are less likely to yield code execution but could support phishing, privilege escalation, or data exposure. MS-ISAC notes no current reports of in-the-wild exploitation for any of these CVEs.
Defenders should prioritize timely patch deployment via automated update mechanisms, since exploitation is characterized as a drive-by compromise vector (T1189) requiring only that a user visit a malicious or compromised page. Standard hardening measures — least-privilege accounts, browser sandboxing/exploit protection, DNS/URL filtering, and user awareness — reduce the blast radius of any future exploitation attempts targeting these flaws.
Mentioned in this report
Source reporting: https://www.cisecurity.org/advisory/multiple-vulnerabilities-in-google-chrome-could-allow-for-arbitrary-code-execution_2026-101
Free public brief. Slack alerts on the vendors you run come with the paid plans, and a new account gets three days of them, no card.
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries live profiles of the CVEs it names. The paid plans add the security research and news reporting the free tier leaves out.
It sits in a corpus of 16,445 reports from 149 sources, 666 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Slack alerts are a paid-plan feature: name the vendors you run and Slack hears about the reports that touch them, not the rest of the week's. Nothing is charged unless you subscribe.
Create a free account What it costs