If you have been putting off restarting Google Chrome, this is a good time to stop postponing it. Google has patched a security vulnerability with an exploit already in the wild, and the update applies to Windows, macOS, and Linux.
The flaw, tracked as CVE-2026-125350, affects Chrome’s XML component. It is one of nine security vulnerabilities addressed in the browser’s November 9 stable release, making this an update worth checking for rather than leaving to chance.
In its release announcement, Google states, “Google is aware that an exploit for CVE-2026-125350 exists in the wild.” An anonymous researcher reported the vulnerability on November 6, and Google rates it as high severity.
The company describes the problem as a use-after-free vulnerability. That means software accesses memory after it has been released, potentially allowing an attacker to interfere with how the program behaves.
Google has not disclosed who was targeted or which operating systems were involved in the observed attacks. The fix covers all three desktop platforms, but that does not establish that attackers have successfully exploited users on each one.
The updated stable versions are 157.0.8103.50/.51 for Windows and macOS, and 157.0.8103.50 for Linux. Google says distribution will take place over the coming days and weeks, so availability may vary.
There is a practical difference between a security researcher demonstrating a bug and an exploit turning up in the wild. Google’s warning puts this vulnerability in the latter category, giving users a concrete reason to prioritize the update.
That does not mean everyone running an earlier Chrome version has been compromised. It means there is a known security problem, a fix is available, and continuing to use an unpatched browser creates an avoidable risk.
To check your version, open Chrome’s three-dot menu, select Help, and then choose About Google Chrome. Google’s update guidance explains that this page displays the current version and checks for available updates.
On Windows and macOS, apply the available update and select Relaunch when prompted. Linux users should update Chrome through their package manager, then close and reopen the browser.
The restart is part of the job. Downloading an update while keeping the same browser session running does not mean you have started using the patched version.
Save anything unfinished before relaunching, especially text sitting in web forms. Chrome normally restores ordinary tabs and windows, but Incognito windows do not reopen automatically, so plan accordingly.
After restarting, return to About Google Chrome and confirm the version number. That small check is more useful than assuming an update notification, a completed download, or a recent computer restart means everything is current.
If Chrome is managed by your employer or school, its update schedule may be controlled by an administrator. Flag the vulnerability and ask whether the patched release has been deployed rather than trying to work around the organization’s software policies.
Administrators should also account for browsers that remain open across long sessions. An updated package on disk and a patched browser actively running on an employee’s computer are not necessarily the same thing.
Users of other Chromium-based browsers should check their browser vendor’s security notices and updates. Chrome’s release numbers do not establish patch status for Microsoft Edge, Brave, Opera, or separately packaged Chromium builds, which have their own release processes.
This is also a reminder to check the browser you actually use, rather than treating an operating-system update as confirmation that every application is covered. Browser maintenance deserves its own attention, particularly when the vendor has already acknowledged an exploit in the wild.
There is no need to turn this into an operating-system rivalry. Whether your computer runs Windows, macOS, or Linux, the immediate task is the same: get the applicable Chrome update, relaunch the browser, and verify the version.
Your open tabs may feel like a carefully maintained filing system at this point. They are still not a good reason to keep an exploited browser vulnerability around.
Support independent tech journalism
NERDS.xyz is independently owned and operated. If you enjoy my coverage of Linux, AI, hardware, cybersecurity, and tech culture, consider supporting the site on Ko-fi.
Support NERDS.xyz
