Google Chrome: update today, attackers are already using a new flaw
10 November 2026Google says an exploit for a new Chrome flaw, CVE-2026-125350, exists in the wild. It is fixed in Chrome 157.0.8103.50: relaunch Chrome today and check the version. Microsoft has not released the Edge fix yet.

What happened
On Monday 09/11/2026 Google released a Chrome update with nine security fixes. One of them, CVE-2026-125350, is a memory bug (Google calls it a "use after free") in the part of Chrome that reads XML, a common format for data on the web. In Google's words: "Google is aware that an exploit for CVE-2026-125350 exists in the wild." So someone already has a working attack for it. Google names an exploit for this one flaw only, not the other eight.
Google says details of the bugs "may be kept restricted until a majority of users are updated with a fix", so little more is known yet. Chrome 157 itself came out on 03/11/2026; that release is covered in our Chrome 157 story.
Does this affect you
Yes, if anyone in your business uses Google Chrome on a Windows PC, a Mac, a Linux computer or an Android phone and it isn't on 157.0.8103.50 or later yet.
Microsoft Edge is built from the same Chromium code. On 09/11/2026 Microsoft wrote that it is "aware of the recent exploits existing in the wild" and is "actively working on releasing a security fix". Its note doesn't name the flaw, and no fixed version of Edge was out when we checked on 10/11/2026.
Brave, Opera and Vivaldi are built on Chromium too. None of them had put out a release since Google's fix when we checked on 10/11/2026.
Google's posts for this fix don't mention Chromebooks or Chrome on iPhone and iPad, so we can't say either way. Install their next updates when offered.
What to do
- On a computer, open Chrome's menu (the three dots at the top right), then Help, then About Google Chrome. Chrome checks for the update and downloads it. Click Relaunch. Google says Chrome reopens your windows and tabs when it restarts, but not Incognito windows. On Windows, Google says to close all Chrome windows and tabs, then open Chrome again.
- On the same page, check the version reads 157.0.8103.50 or later (Windows and Mac may show .51). Google is rolling the update out "over the coming days/weeks", so if your Chrome doesn't offer it yet, check again later today, and don't count yourself covered until the number matches.
- On an Android phone, open the Play Store, tap your profile icon, then Manage apps and device, find Chrome under Updates available and tap Update. Google says 157.0.8103.50 reaches Google Play "over the next few days". To see your version, open Chrome's menu, then Settings, then About Chrome.
- At work, ask your IT person to make sure every PC restarts Chrome today. Google says a downloaded update applies the next time Chrome restarts, and without a policy Chrome only changes its menu icon and waits for the user. Google's admin setting "Relaunch notification", set to "Force relaunch after a period", makes Chrome restart within a time your IT person chooses, from 1 to 168 hours. If your IT company keeps PCs on Chrome's slower Extended Stable channel, they need 156.0.8078.96 or later, which also has this fix.
- If you use Microsoft Edge, update it as soon as Microsoft releases the fix: Settings and more (the three dots), then Help and feedback, then About Microsoft Edge, and Restart if asked. Check again each day until a new version appears.
- If you use Brave, Opera or Vivaldi, install their next update as soon as it's offered.
Is it being attacked?
Yes, according to Google: "Google is aware that an exploit for CVE-2026-125350 exists in the wild." Google hasn't said who is being targeted or how, and SecurityWeek reports that "no information appears to be available on the attacks". CISA had not added the flaw to its Known Exploited Vulnerabilities list when we checked (catalogue 2026.11.09, released 09/11/2026).
Found by
Google credits the exploited flaw to "anonymous", reported on 06/11/2026, three days before the fix. Nothing published says how it was found, so the tag is not stated.
For developers
- CVE-2026-125350: High (Google's rating), "Use after free in XML", Chromium issue 582442907, "Reported by anonymous on 2026-11-06". No CVE record yet (the CVE API answers CVE_RECORD_DNE) and no NVD entry, so there is no CVSS score (checked 10/11/2026).
- Desktop: 157.0.8103.50 (Linux) and 157.0.8103.50/.51 (Windows, Mac), up from 157.0.8103.39, with "9 security fixes". Android: 157.0.8103.50; Google says Android releases "contain the same security fixes as their corresponding Desktop releases" unless otherwise noted. Extended Stable: 156.0.8078.96 (Windows, Mac), 11 security fixes, including CVE-2026-125350 and three more of this release's nine (CVE-2026-125345, CVE-2026-125346, CVE-2026-125347).
- The other eight, in Google's words: High CVE-2026-125345 "Uninitialized resource in WebGL" (Google); High CVE-2026-125347 "Incorrect authorization in FileSystem" (Google); High CVE-2026-125343 "Buffer overflow in Compositing" (Google); High CVE-2026-125348 "Out of bounds write in GPU" (Google); High CVE-2026-125344 "Type confusion in V8" (Google); High CVE-2026-125346 "Use after free in XML" (Arni Hardarson, Neonix Security); Medium CVE-2026-125349 "Uninitialized resource in GPU" (Google); Medium CVE-2026-125342 "Uninitialized resource in GPU" (Vo Duc Thang, ugvxb). Google names no exploit for any of these.
- Microsoft Edge security release notes, 09/11/2026: "Microsoft is aware of the recent exploits existing in the wild. We are actively working on releasing a security fix." The newest Edge Stable listed is 157.0.4341.42 (05/11/2026), from before Google's fix. A second entry of 09/11/2026 lists Edge 157.0.4341.42 for Android and iOS; it doesn't mention this flaw, so don't read it as the fix.
- Chromebooks: Google's help says Chrome on a Chromebook updates with ChromeOS. The newest ChromeOS Stable post (06/11/2026) is on browser 156.0.8078.93, from before this fix, and no ChromeOS post since mentions CVE-2026-125350. Google hasn't said whether ChromeOS is affected.
- iPhone and iPad: the newest Chrome for iOS release is 157.0.8103.37 (03/11/2026). Google's posts of 09/11/2026 don't mention iOS.
- Other Chromium browsers, checked 10/11/2026: Brave's newest desktop release, 1.99.55 (05/11/2026), runs Chromium 157.0.8103.39; Opera's newest stable is 139.0.6053.38 (04/11/2026); Vivaldi's newest is 8.3 (05/11/2026). All three came out before Google's fix.
- Managed Chrome: the RelaunchNotification policy (set to "Relaunch required") with RelaunchNotificationPeriod. In the Google Admin console: Devices, Chrome, Settings, Chrome updates, Relaunch notification, "Force relaunch after a period", 1 to 168 hours (unset is 168). In Windows Group Policy: "Notify a user that a browser relaunch or device restart is recommended or required".
- SecurityWeek (10/11/2026): "This is the eighth Chrome zero-day exploited this year".
- CISA KEV: not in catalogue 2026.11.09 (released 09/11/2026 19:54 UTC), checked 10/11/2026.
Sources
- Chrome Releases, Stable Channel Update for Desktop, 09/11/2026
- Chrome Releases, Chrome for Android Update, 09/11/2026
- Chrome Releases, Extended Stable Update for Desktop, 09/11/2026
- Chrome Releases, Stable Channel Update for ChromeOS, 06/11/2026
- Microsoft, release notes for Microsoft Edge security updates
- Microsoft Support, getting the latest Microsoft Edge update
- Google Chrome Help, Update Google Chrome
- Google Chrome Enterprise Help, Notify users to restart to apply pending updates
- Brave, release notes
- Opera, desktop blog
- Vivaldi, blog
- CISA KEV JSON catalogue 2026.11.09
- SecurityWeek, 10/11/2026
Read next
More from The Patch Wave
- Act today

iPhones, iPads and Macs: update today, Apple has patched a compression flaw already on the US exploited list
Apple's 09/11/2026 updates fix the Brotli flaw CVE-2026-111497, which CISA added to its exploited list on 27/10/2026, and an iMessage group chat flaw. Update iPhones, iPads and Macs today.
- Act today

Microsoft Outlook: November's updates fix a flaw attackers are already using
Microsoft says attackers are already using an Outlook flaw (CVE-2026-124194) fixed in this month's updates. Update Office and run Windows Update today.
- Watch

Hotmail and Outlook.com bounced some business email for nearly three days: Microsoft has fixed it
Microsoft says a faulty spam rule update made Outlook.com, Hotmail and Live wrongly block some email from 06/11 to 09/11/2026. It has rolled the update back. If your mail to those addresses still bounces, tell your IT person.