CVE-2026-125350 is an actively exploited Chrome zero-day, and you are protected once Chrome shows 157.0.8103.50 or later on Linux, or 157.0.8103.50/.51 or later on Windows and Mac. Open Help > About Google Chrome to check, let it update, and click Relaunch. Edge, Brave, Opera, and Vivaldi have also shipped fixes, so update those too.
On November 9, 2026, Google released an emergency Chrome update and warned that it is "aware that an exploit for CVE-2026-125350 exists in the wild." The bug is a high-severity use-after-free flaw in Chrome's XML component.
One day later, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added it to its Known Exploited Vulnerabilities (KEV) catalog. According to BleepingComputer and The Hacker News, it is the eighth Chrome zero-day exploited in attacks in 2026.
So what does the flaw do? Which version do you need? And does it affect Edge, Brave, Opera, Vivaldi, or Chrome on your phone?
Here is everything you need to know, including the exact fixed version for each browser and how to update it.
What Is CVE-2026-125350?
CVE-2026-125350 is a use-after-free vulnerability in the XML component of Google Chrome. The official CVE record describes it this way:
"Use after free in XML in Google Chrome prior to 157.0.8103.50 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page."
In plain English, a use-after-free bug happens when a program frees a piece of memory but then keeps using it. An attacker who can control what ends up in that memory may be able to crash the browser or run their own code.
Here are the key details:
- CVE ID: CVE-2026-125350
- Weakness: Use after free (CWE-416)
- Component: XML
- Chromium severity: High
- CVSS 3.1 score: 8.8 (High), scored by CISA, with vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Attack method: A crafted web page. The attack works over the network and needs no login, but the victim has to do something, such as opening a malicious page.
- Exploited in the wild: Yes, according to Google
- First fixed in: Chrome 157.0.8103.50 (released November 9, 2026)
Google's release notes credit two reports for the bug: one from Arni Hardarson (Neonix Security) on October 12, 2026, and one from an anonymous reporter on November 6, 2026.
"Inside the sandbox" means the attacker's code starts inside Chrome's restricted sandbox. Attackers often chain a bug like this with a second flaw to escape the sandbox. Google has not said whether that happened here.
Is CVE-2026-125350 Being Exploited?
Yes. Google's November 9 advisory says: "Google is aware that an exploit for CVE-2026-125350 exists in the wild."
Google has not shared who is behind the attacks, who was targeted, or how the exploit was delivered. As usual, it is keeping bug details restricted "until a majority of users are updated with a fix."
CISA added the flaw to the KEV catalog on November 10, 2026, under the name "Google Chromium Use-After-Free Vulnerability." It set a deadline of November 24, 2026 for U.S. federal civilian agencies to patch. CISA lists known ransomware use as "Unknown."
CISA's entry also notes that the flaw "could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera." That is why this is not only a Chrome problem.
Am I Affected?
You are likely affected if you use a Chromium-based browser that has not updated since November 9, 2026. That includes:
- Google Chrome below 157.0.8103.50 (Linux) or 157.0.8103.50/.51 (Windows and Mac)
- Chrome Extended Stable below 156.0.8078.96
- Microsoft Edge below 157.0.4341.46
- Brave below 1.99.56
- Opera below 140.0.6074.17
- Vivaldi older than the second 8.3 minor update (Chromium 156.0.8078.99)
- Chrome for Android below 157.0.8103.50
Chrome updates itself in the background, but the fix only takes effect after the browser restarts. If you leave Chrome open for days, you may still be running the old version even though the update has been downloaded.
CVE-2026-125350 Fixed Versions for Every Browser
The table below lists the first version of each browser with the fix, plus the newer version you should aim for as of November 17, 2026. All versions come from the vendors' own release notes.
| Browser | First version with the fix | Released | Newer version to aim for |
|---|---|---|---|
| Chrome (Windows, Mac) | 157.0.8103.50/.51 | Nov 9, 2026 | 157.0.8103.78/.79 (Nov 11) |
| Chrome (Linux) | 157.0.8103.50 | Nov 9, 2026 | 157.0.8103.78 (Nov 11) |
| Chrome Extended Stable (Windows, Mac) | 156.0.8078.96 | Nov 9, 2026 | 156.0.8078.100 (Nov 11) |
| Chrome for Android | 157.0.8103.50 | Nov 9, 2026 | 157.0.8103.78 (Nov 11) |
| Microsoft Edge (desktop Stable) | 157.0.4341.46 | Nov 9, 2026 | 157.0.4341.57 (Nov 13) |
| Microsoft Edge for Android | 157.0.4341.53 | Nov 11, 2026 | 157.0.4341.53 |
| Brave (desktop) | 1.99.56 (Chromium 157.0.8103.50) | Nov 10, 2026 | 1.99.57 (Nov 12) |
| Brave (Android) | 1.99.56 | Nov 11, 2026 | 1.99.57 (Nov 12) |
| Opera (desktop) | 140.0.6074.17 | Nov 10, 2026 | 140.0.6074.18 (Nov 11) |
| Vivaldi (desktop) | 8.3, minor update 2 (Chromium 156.0.8078.99) | Nov 10, 2026 | 8.3, minor update 3 (Nov 13) |
A few notes on the table:
- Opera says Opera 140 is based on Chromium 157.0.8103.39, which is older than Google's fixed build. Its changelog shows the CVE-2026-125350 fix was cherry-picked into that build, so the Chromium number alone does not tell the whole story.
- Vivaldi stays on Chromium 156 Extended Stable but pulls in security fixes from Chromium 157. Its November 10 update names the CVE-2026-125350 fix directly.
- For Chrome on Windows and Mac, Google ships two build numbers (for example, .50 and .51) that differ by the last digit. Either one includes the fix.
What Is the Latest Chrome Version Right Now?
Aiming for the first fixed version is the minimum. It is better to be on the newest build.
On November 11, 2026, Google shipped Chrome 157.0.8103.78/.79 for Windows and Mac and 157.0.8103.78 for Linux. That update includes 83 security fixes, and 5 of them are rated Critical, all use-after-free bugs in components such as ServiceWorker, CSS, Layout, Skia, and Accessibility. Google has not said that any of those 83 are being exploited.
As of November 17, 2026, Google's public VersionHistory data shows:
- Windows and Mac: 157.0.8103.79 rolled out to nearly all Stable users
- Linux: 157.0.8103.78
- Android: 157.0.8103.78
- Extended Stable: 156.0.8078.100
Google has also started an "early stable" rollout of Chrome 158 (158.0.8127.36/.37) to a small percentage of Windows users, with Mac to follow. If you see version 158, you are also covered.
How to Update Google Chrome
Windows, Mac and Linux
- Open Chrome and click the three-dot menu in the top-right corner.
- Go to Help > About Google Chrome. You can also type
chrome://settings/helpin the address bar. - Chrome checks for updates and downloads the latest version.
- Click Relaunch. Save any work in web apps first.
- Check the version number again. It should be 157.0.8103.50 or higher.
On Linux, Chrome usually updates through your system's package manager. On Debian or Ubuntu with Google's repository installed, you can run:
sudo apt update && sudo apt install --only-upgrade google-chrome-stable
Tip: If the About page says Chrome is up to date but shows an older version, Google may still be rolling it out. Check again later in the day and restart the browser.
Chrome for Android
- Open the Google Play Store.
- Tap your profile picture, then Manage apps & device.
- Under Updates available, find Chrome and tap Update.
- To confirm, open Chrome, tap the three-dot menu, then Settings > About Chrome. It should show 157.0.8103.50 or later.
Google says Chrome for Android releases contain the same security fixes as the matching desktop releases unless otherwise noted.
Chrome for iPhone and iPad
Chrome on iOS is built on Apple's WebKit engine, not Chrome's own engine, and Google's iOS release notes for November 2026 do not mention CVE-2026-125350. Google released Chrome 158 for iOS (158.0.8127.35) on November 12. Update it from the App Store anyway, and keep iOS itself updated, since WebKit fixes arrive through Apple's system updates.
How to Update Microsoft Edge
Microsoft's Edge security release notes say Edge Stable 157.0.4341.46 (November 9) contains a fix for CVE-2026-125350. Edge for Android 157.0.4341.53 (November 11) also includes the fix. The newest Edge Stable is 157.0.4341.57, released November 13.
- Open Edge and click the three-dot menu (Settings and more).
- Go to Help and feedback > About Microsoft Edge, or type
edge://settings/help. - Let Edge download the update, then click Restart.
On Android, update Edge from the Google Play Store. Edge is installed on every Windows 11 PC, so update it even if you never use it. If you are also checking your other Windows updates, our guide to the Windows 11 November update covers what else changed this month.
How to Update Brave, Opera and Vivaldi
Brave
Brave 1.99.56 moved to Chromium 157.0.8103.50 on November 10 for desktop and November 11 for Android. Brave 1.99.57 (November 12) moved to Chromium 157.0.8103.79.
- Desktop: Open the menu and choose About Brave, or go to
brave://settings/help. Let it update, then click Relaunch. - Android: Update Brave from the Google Play Store.
Opera
Opera 140 became the Stable version on November 10, and its release notes list "Fixed a security vulnerability (CVE-2026-125350)." The changelog shows the fix in build 140.0.6074.17, followed by 140.0.6074.18 on November 11.
- Open the Opera menu and choose Update & Recovery, or type
opera://update. - Click Check for update, then restart Opera.
Vivaldi
Vivaldi's second 8.3 minor update for desktop (November 10) moved to Chromium 156.0.8078.99 ESR, which Vivaldi says includes the CVE-2026-125350 fix. The third minor update (November 13) moved to 156.0.8078.104 ESR, with security fixes from Chrome 157.0.8103.78/79.
- On Windows and Linux, open the Vivaldi menu > Help > Check for Updates.
- On Mac, choose Vivaldi > Check for Updates from the menu bar.
- On Android, update Vivaldi from the Google Play Store.
What Should IT Teams and Businesses Do?
If you manage computers for a company or school, treat this as urgent:
- Patch before November 24. That is CISA's KEV deadline for U.S. federal agencies, and it is a sensible target for everyone else.
- Force a relaunch. Use Chrome or Edge enterprise policies to require a browser restart after updates. Downloaded updates do nothing until the browser restarts.
- Check every Chromium browser. Staff may have Brave, Opera, or Vivaldi installed next to Chrome and Edge.
- Don't forget Extended Stable. Organizations on Chrome's Extended Stable channel need 156.0.8078.96 or later (156.0.8078.100 is current).
- Watch other software too. Browser bugs are not the only urgent fixes this month. Server admins should also review our guides to the Node.js Brotli vulnerability CVE-2026-111497 and the PHP2Shell flaws putting web servers at risk.
How to Stay Safe Until You Update
Until every device is patched, a few habits lower your risk:
- Restart your browser now. This is the single most useful step.
- Be careful with unexpected links, especially in email, chat apps, and social media messages. This bug is triggered by a crafted web page.
- Only update from official sources. Use the browser's own About page, Google Play, or the App Store. Fake "Chrome update" pop-ups are a common way to spread malware. Our report on FaceStealer fake Zoom and Teams calls shows how attackers use fake update and app prompts.
- Keep automatic updates on for your browsers and your operating system.
Frequently Asked Questions
What Chrome version fixes CVE-2026-125350?
Chrome 157.0.8103.50/.51 for Windows and Mac and 157.0.8103.50 for Linux, released November 9, 2026. On the Extended Stable channel, the fix is in 156.0.8078.96. Any newer version, such as 157.0.8103.78/.79, also includes it.
Is CVE-2026-125350 a zero-day?
Yes. Google confirmed that an exploit exists in the wild, and CISA added it to the Known Exploited Vulnerabilities catalog on November 10, 2026. BleepingComputer and The Hacker News report it is the eighth exploited Chrome zero-day of 2026.
Does CVE-2026-125350 affect Microsoft Edge?
Edge is built on Chromium, and Microsoft says Edge Stable 157.0.4341.46 and Edge for Android 157.0.4341.53 contain the fix. Go to edge://settings/help to update.
Is Chrome on iPhone affected?
Chrome on iOS uses Apple's WebKit engine, and Google's iOS release notes do not list CVE-2026-125350. Still keep Chrome and iOS updated through the App Store and Settings.
Final Thoughts
CVE-2026-125350 is a high-severity, actively exploited flaw in the code Chrome and other Chromium browsers use to process XML. Google has not shared attack details, but CISA's KEV listing makes it clear this is not a theoretical risk.
The fix is simple: get Chrome to 157.0.8103.50 or later (ideally 157.0.8103.78/.79), update Edge, Brave, Opera, and Vivaldi to their patched versions, and restart each browser.
If you do only one thing today, open your browser's About page and click Relaunch.
Sources and Further Reading
- Stable Channel Update for Desktop, November 9, 2026 (Chrome Releases)
- Extended Stable Update for Desktop, November 9, 2026 (Chrome Releases)
- Stable Channel Update for Desktop, November 11, 2026 (Chrome Releases)
- Chrome for Android Update, November 9, 2026 (Chrome Releases)
- Early Stable Update for Desktop (Chrome 158) (Chrome Releases)
- CVE-2026-125350 (CVE.org)
- CVE-2026-125350 Detail (NIST NVD)
- Known Exploited Vulnerabilities Catalog: CVE-2026-125350 (CISA)
- Release notes for Microsoft Edge Security Updates (Microsoft Learn)
- Brave Release Notes (Brave)
- Opera 140 Stable and Changelog for 140 (Opera)
- Minor update (2) for Desktop 8.3 and Minor update (3) for Desktop 8.3 (Vivaldi)
- Google patches eighth Chrome zero-day exploited in attacks this year (BleepingComputer)
- Google Issues Chrome Security Update for Eighth Actively Exploited Zero-Day of 2026 (The Hacker News)
- Update Google Chrome (Google Chrome Help)
Information in this article reflects vendor advisories, the CVE and NVD records, and CISA's KEV catalog available on November 17, 2026. Version numbers and rollout status may change as new updates are released.
Cover photo: Yuri Samoilov via Wikimedia Commons, CC BY 3.0
The conversation (0)
Different perspectives make better conversations. Keep it thoughtful.
Be the first to share a perspective.