Chrome 158 patches 204 vulnerabilities, including 6 critical
Google released Chrome 158 with fixes for 204 vulnerabilities, six critical; no exploitation is reported, so update to 158.0.8127.36 or later.
- Published
- CVE
- CVE-2026-130963
CVE-2026-131054
CVE-2026-131031
CVE-2026-131060
CVE-2026-131008
CVE-2026-130975
CVE-2026-130910 - Ecosystem
- Desktops, browsers and mobile
- Fixed in
- Chrome 158.0.8127.36 (Linux), 158.0.8127.36/.37 (Windows and macOS)
- Exploitation
- No, SecurityWeek and GBHackers both say Google’s advisory does not report exploitation in the wild
What happened
Google released Chrome 158 to the stable channel on Tuesday, November 17, 2026, according to GBHackers and SecurityWeek. The update patches 204 vulnerabilities, including six critical-severity bugs.
SecurityWeek breaks the 204 down as 6 critical, 62 high, 82 medium and 54 low severity. The most common weakness type is use-after-free, with 51 occurrences.
GBHackers says all six critical issues involve memory safety: three use-after-free flaws, two out-of-bounds writes and one buffer overflow. It names these critical CVEs:
- CVE-2026-130963: use-after-free in WebView
- CVE-2026-131054: out-of-bounds write in ANGLE
- CVE-2026-131031: out-of-bounds write in GPU
- CVE-2026-131060: buffer overflow in Media
- CVE-2026-131008: use-after-free in GarbageCollection
- CVE-2026-130975: use-after-free in WebAudio
GBHackers also lists high-severity fixes in V8 (use-after-free), Omnibox (incorrect authorization), Extensions (missing authorization) and Autofill. It notes that the advisory’s total of 204 fixes is broader than its itemized CVE list.
On rewards, SecurityWeek reports that no bounty will be paid for the critical bugs, and none for 163 of the flaws overall. Google found 145 of those and Xinyang Ge found 15. Google paid $11,000 for five externally reported flaws and has yet to decide the amounts for 36 more. GBHackers adds a $4,000 reward for CVE-2026-130910, an ANGLE protection mechanism failure. It also says Google credited Xinyang Ge of Anthropic, assisted by Claude, with the GPU and Media critical reports.
Exploitation: SecurityWeek says Google makes no mention of any of these vulnerabilities being exploited in the wild. GBHackers says the same of the Stable channel advisory.
Severity ratings differ by outlet. HKCERT rates the bulletin Medium Risk. It says a remote attacker could exploit some of the flaws to cause denial of service, spoofing, security restriction bypass, information disclosure and remote code execution. SecurityWeek and GBHackers report six critical-severity bugs.
Am I affected?
You are affected if you run Google Chrome on any of these platforms at a version below the fixed builds, per HKCERT:
- Linux: prior to 158.0.8127.36
- macOS: prior to 158.0.8127.36/.37
- Windows: prior to 158.0.8127.36/.37
GBHackers says the update reaches users over the coming days and weeks, so your browser may not have it yet. Whether other Chromium-based browsers are affected is not confirmed in the sources.
What to do now
- Update Chrome to 158.0.8127.36 or later on Linux, or 158.0.8127.36/.37 or later on Windows and macOS (HKCERT, SecurityWeek).
- On desktop, open the Chrome menu, select Help > About Google Chrome, let the browser check for the new build, and relaunch if prompted. Then return to the same page to confirm the installed version (GBHackers).
- In managed environments, check the running version across endpoints rather than treating an available or downloaded update as installed (GBHackers).
- HKCERT advises visiting the vendor website for details before installing (HKCERT).