Critical CVSS 9.6 Security news
Chrome 158 ships 204 security fixes: six critical flaws, two of them reaching outside the sandbox
Google promoted Chrome 158 to the stable channel on Tuesday 17 November 2026 with 204 security fixes. Chromium rates six of the bugs as critical, and according to their NVD records two of them let an attacker run code outside the browser sandbox simply by getting the victim to open a crafted page. Google does not report any exploitation. The update rolls out gradually, so trigger it manually and restart the browser.
Key points
- Who is affected: anyone running Chrome on a computer and, according to its NVD record, Chrome on Android (the WebView component).
- The flaws: six critical bugs in GPU, ANGLE, WebView, Media, GarbageCollection and WebAudio. For two of them NVD describes code execution outside the sandbox from a crafted page; for WebView, from crafted network traffic.
- Exploited: no, Google does not mention an exploit in the wild. Four of the six critical bugs were reported by Xinyang Ge of Anthropic, two of them with assistance from the Claude model.
- What to do: update and restart Chrome; admins should enforce the version through policy. Microsoft was still working on an Edge fix on 17 Nov.
Vulnerabilities: CVE-2026-131031, CVE-2026-131054, CVE-2026-130963, CVE-2026-131060, CVE-2026-131008, CVE-2026-130975
What happened
On the evening of 17 November 2026 (11:12 Pacific time) Google promoted Chrome 158 to the stable channel: 158.0.8127.36 for Linux and 158.0.8127.36/.37 for Windows and Mac. The release contains 204 security fixes. Chromium rates six of the bugs as critical and dozens as high. The same day Google also shipped Extended Stable 156.0.8078.108/.109 for Windows and Mac with 79 security fixes.
Google does not say an exploit exists in the wild for any of the bugs. It says the update will roll out "over the coming days/weeks".
| Bug | Component and type | Impact per NVD | CVSS 3.1 (CISA in NVD) |
|---|---|---|---|
| CVE-2026-131031 | GPU - out-of-bounds write | code outside the sandbox, crafted page | 9.6 |
| CVE-2026-131054 | ANGLE - out-of-bounds write | code outside the sandbox, crafted page | 9.6 |
| CVE-2026-130963 | WebView (Chrome on Android) - use-after-free | code outside the sandbox, crafted network traffic | not yet |
| CVE-2026-131060 | Media - buffer overflow | code inside the sandbox, crafted page | 8.8 |
| CVE-2026-131008 | GarbageCollection - use-after-free | code inside the sandbox, crafted page | 8.8 |
| CVE-2026-130975 | WebAudio - use-after-free | code inside the sandbox, crafted page | 8.8 |
Technical details
Most of the critical bugs are classic memory-safety errors: use-after-free (the program keeps using memory it has already released), out-of-bounds writes and buffer overflows. If an attacker can trigger one of these from web content, they can corrupt the browser's memory and run their own code.
What matters most is where that code runs. Chrome renders pages in an isolated process (the sandbox) with limited access to the system. An attacker who only gets code running inside the sandbox usually needs a second bug to break out. For CVE-2026-131031 (GPU) and CVE-2026-131054 (ANGLE, the layer Chrome uses to draw 3D graphics and WebGL), however, the NVD records describe code execution outside the sandbox directly - the victim only has to open a crafted page. That is why both score 9.6 with a scope change (S:C).
The most unusual entry is CVE-2026-130963 in WebView, the component Android apps use to display web content. NVD files it under Chrome on Android and names crafted network traffic, not a web page, as the trigger, with impact outside the sandbox. There is no CVSS score or further detail yet. Google usually keeps bug details restricted until most users have the fix. We do not publish exploitation guidance either.
The release post credits a reporter for each bug. Four of the six critical ones were reported by Xinyang Ge of Anthropic, two of them (GPU and Media) noted as assisted by Claude. Google found the remaining two itself.
Who is affected
- Chrome for Windows and Mac before 158.0.8127.36/.37 and for Linux before 158.0.8127.36.
- Extended Stable (the eight-week update cadence many organisations use) before 156.0.8078.108/.109.
- Chrome on Android - the WebView bug. We could not find a separate Google post on Chrome 158 for Android when we checked on 18 Nov; update Chrome and Android System WebView from Google Play as soon as they are offered.
- Other Chromium-based browsers. On 17 Nov Microsoft said in its Edge security notes that it is aware of the Chromium fixes and is working on a fix. The latest stable Edge, 157.0.4341.57, dates from 13 Nov.
How to tell if you were compromised
Google says none of the bugs is being exploited and nobody has published indicators of compromise. For admins, the useful work right now is inventory:
- List devices still running an older Chrome from your device management or software inventory, and track how many remain after a few days.
- Find browsers that have not been restarted in a long time. A downloaded update only takes effect after a relaunch.
- Watch EDR for unusual child processes of the browser (command shell, PowerShell, script interpreters) - a generic detection that also helps against future exploits.
- If Google or a CERT later publishes indicators, you can pull them out of the text with our IOC extractor. You can recompute scores from CVSS vectors in our CVSS calculator.
What to do
- Update and restart Chrome: Menu → Help → About Google Chrome.
- On Android, update Chrome and Android System WebView from Google Play.
- Admins: deploy 158.0.8127.36/.37, or 156.0.8078.108/.109 on Extended Stable, and force a browser relaunch through policy. Do not wait for the staged rollout.
- Edge and other Chromium-based browsers: install your vendor's next security update. We will add Edge once Microsoft ships its fix.
Timeline
Update
- 18 Nov 2026: first version.
FAQ
How do I check that I have Chrome 158?
Open the menu and choose Help → About Google Chrome. Chrome checks for updates and offers to relaunch. The version should start with 158.0.8127.36 (.37 is also possible on Windows and Mac). Organisations on Extended Stable should be on 156.0.8078.108 or .109.
Are attackers exploiting any of these bugs?
Not according to Google. The Chrome 158 release post does not say an exploit exists in the wild for any of the fixes, and neither do the NVD records. Attackers often study critical browser bugs once a fix is public, though, so do not put the update off.
Does this affect Edge, Brave or Opera?
Chromium-based browsers can contain the same code. On 17 Nov Microsoft wrote in its Edge security notes that it is aware of the recent Chromium security fixes and is working on an Edge fix. For other browsers, watch for your vendor's update.
Why is Claude mentioned next to some bugs?
Google credits the reporter of each bug in its release post. Four of the critical bugs were reported by researcher Xinyang Ge of Anthropic, two of them noted as assisted by the Claude model. In the interest of transparency: Kyberkit's content is also produced by Anthropic's Claude under the site owner's supervision.
Sources
- Google Chrome Releases - Stable Channel Update for Desktop (17 Nov 2026)
- NVD - CVE-2026-131031 (GPU, CVSS 9.6)
- NVD - CVE-2026-131054 (ANGLE, CVSS 9.6)
- NVD - CVE-2026-130963 (WebView on Android)
- Microsoft Learn - Release notes for Microsoft Edge Security Updates (17 Nov 2026)
- Google Chrome Help - Update Google Chrome
Spotted a mistake? Let us know and we will correct it openly.