How to use
- Open this page in the Chrome you want to check. On a computer or Android phone the checker reads the full version by itself; otherwise type it from About Google Chrome.
- Read the verdict: Protected, Update to the Stable build, or Update now. The table under it lists the first safe builds.
- If Chrome is behind, open About Google Chrome so it downloads the update, then press Relaunch. The fix only runs after Chrome restarts.
- Come back and check again. On a work computer that is managed by IT, ask them if the update does not arrive.
What a Chrome zero-day is
A zero-day is a flaw that attackers are already using before most people have the fix. For Chrome it usually means a booby-trapped web page: you open a link, and the page uses the bug to run code on your computer or phone, often as the first step of spyware or account theft. Google says so in its release notes with one sentence: "Google is aware that an exploit for this CVE exists in the wild."
On November 9, 2026, Google wrote that sentence for CVE-2026-125350, the eighth Chrome zero-day of 2026. It did not say who used it or against whom, which is normal: details stay private until most users have updated.
What causes CVE-2026-125350, in plain words
Web pages can contain XML, a format for structured data that Chrome reads with its XML parser. While parsing, the browser creates small objects in memory and throws them away when they are no longer needed. In this bug, one part of the parser throws an object away but keeps a note of where it was. Later it follows that note and uses memory that now belongs to something else. That is a use after free.
An attacker who controls the XML can arrange what gets written into that freed memory, so the browser ends up following the attacker's data instead of its own. That is how a page turns a memory mistake into running its own code. Chrome's sandbox still limits what that code can do, which is why real attacks usually chain a second bug to escape it.
Which versions are safe
Google fixed CVE-2026-125350 in Chrome 157.0.8103.50 for Windows, Mac and Linux (.51 on some Windows and Mac machines) and in the same build for Android. Companies on the Extended Stable channel got it in 156.0.8078.96. Chrome 158 reached the Stable channel on November 17, 2026 as 158.0.8127.36 (Android 158.0.8127.42), and it includes the fix too.
Chrome on iPhone and iPad is different: Apple requires every browser there to use its WebKit engine, so Google's desktop and Android advisory does not apply. Keep iOS and the Chrome app updated from the App Store.
| Channel | First version with the fix |
|---|---|
| Stable, Windows, Mac and Linux | 157.0.8103.50 |
| Extended Stable, Windows and Mac | 156.0.8078.96 |
| Android | 157.0.8103.50 |
| Chrome 158 Stable | 158.0.8127.36 |
Why Chrome can be out of date even with automatic updates
Chrome downloads updates in the background, but the new version only runs after a relaunch. People who keep the browser open for weeks, or put the computer to sleep instead of shutting it down, can run an old version long after the fix was released. A colored Update button in the top-right corner means a relaunch is waiting.
Google also rolls updates out over days or weeks, so some machines get them later. Opening About Google Chrome makes it check right away. On work computers, IT can hold back or delay updates through policy, and Chrome stops updating on operating systems it no longer supports.
Chrome zero-days exploited in 2026
Each of these was fixed in the Chrome update released when Google announced it, so a current Chrome has all of them.
| CVE | Flaw | Fixed |
|---|---|---|
| CVE-2026-2441 | Iterator invalidation in CSS font features | February |
| CVE-2026-3909 | Out-of-bounds write in Skia (2D graphics) | March |
| CVE-2026-3910 | Inappropriate implementation in V8 (JavaScript) | March |
| CVE-2026-5281 | Use after free in Dawn (WebGPU) | April |
| CVE-2026-11645 | Out-of-bounds read and write in V8 | June |
| CVE-2026-87491 | Out-of-bounds write in V8 | September |
| CVE-2026-85046 | Type confusion in V8 | September |
| CVE-2026-125350 | Use after free in XML | November |
Edge, Brave, Opera and other Chromium browsers
These browsers are built on Chromium, the open-source core of Chrome, so they usually carry the same bugs. Each vendor ships the fix in its own version number on its own schedule, so a Chrome version number tells you nothing about them. Update them from their own About page and check the vendor's release notes for the CVE.
Frequently asked questions
How do I see my exact Chrome version?
Click the three-dot menu, then Help, then About Google Chrome. You can also type chrome://version in the address bar. Use all four numbers, for example 157.0.8103.51; the first number alone is not enough.
Why does this page sometimes show the version by itself and sometimes not?
Chrome on computers and Android can share its full version with a page through a browser feature called user-agent client hints. Firefox, Safari, Chrome on iPhone and some Chromium browsers don't, so you type it in.
I updated but the checker still says update. Why?
Chrome needs a relaunch. Click Relaunch on the About page or close every Chrome window, then open this page again. Tabs come back when Chrome restarts.
Does antivirus protect me instead of updating?
Not reliably. These attacks run inside the browser's own memory from an ordinary web page, which security software often can't see. Updating Chrome is the only fix.
Is anything sent to fbuff?
No. The check runs in your browser. The version number is read and compared on your device and never uploaded.