CERT-FR flags 47 Chrome vulnerabilities
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
CERT-FR advisory lists 47 CVEs fixed in Google Chrome and Chrome Extended Stable; severity and exploitation details are unspecified by Google.
CERT-FR has published an advisory summarizing a Google Chrome stable channel security update addressing 47 CVEs across Chrome and Chrome Extended Stable for Windows, Mac, and Linux. Affected versions include Chrome Extended Stable prior to 152.0.7977.167 (Windows/Mac) and Chrome 155.x prior to 155.0.8059.79 (Linux/Windows) and 155.0.8059.80 (Mac). The advisory does not specify the nature or severity of the vulnerabilities (memory corruption, type confusion, use-after-free, etc.) as this information was not detailed by the vendor at the time of publication; CERT-FR characterizes the impact generically as allowing an attacker to cause an unspecified security issue.
No indication of active exploitation in the wild is provided in this advisory. Defenders should treat this as a routine browser patch cycle and prioritize updating to the fixed versions referenced in Google's own Chrome Releases blog posts dated October 13, 2026, which will contain the authoritative per-CVE technical details once published by Google.
Given the volume of CVEs (47) bundled into a single browser release and the lack of any reported in-the-wild exploitation or proof-of-concept activity, this should be treated as standard patch management guidance rather than an urgent incident response matter. Organizations managing Chrome deployments at scale, especially those on the Extended Stable channel, should schedule the update through normal patch cycles.
Mentioned in this report
Source reporting: https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-1308
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 its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,854 reports from 146 sources, 616 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. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs