Plexus Access Solution

Chrome's eighth exploited zero-day of 2026: update your browsers now

Google has fixed an actively exploited use-after-free flaw in Chrome's XML component. It is the eighth Chrome zero-day exploited this year, and the fix is only useful once every browser in the office has actually restarted on the new version.

Key takeaways

  • Google says an exploit for CVE-2026-125350 exists in the wild, so this is not a theoretical risk.
  • The fix is in Chrome 157.0.8103.50 or later; the browser must restart to finish updating.
  • Google has not shared how the flaw is being exploited, so treat every unpatched browser as exposed.
  • Check other Chromium-based browsers and managed devices, not only Chrome on office PCs.

What happened

In its weekly recap published on 16 November 2026, The Hacker News reported that Google patched an actively exploited, high-severity flaw in Chrome, tracked as CVE-2026-125350. It is rated 8.8 on the CVSS scale, the standard 0 to 10 score for how serious a vulnerability is. The recap describes it as a use-after-free bug in Chrome's XML component.

A use-after-free is a memory error. A program frees a piece of memory but keeps a pointer to it, and an attacker can then abuse that stale pointer to run their own code. BleepingComputer, which covered the fix on 10 November, describes the flaw as sitting in the XML parser, where an object is deleted but its pointer is not cleared.

According to BleepingComputer, Google said it is aware that an exploit for CVE-2026-125350 exists in the wild. Google has not said how or in what context the flaw is being exploited, and it may keep bug details restricted until most users have updated.

The fixed builds reported by The Hacker News are 157.0.8103.50 and 157.0.8103.51 for Windows and macOS, and 157.0.8103.50 for Linux. BleepingComputer counts this as the eighth Chrome zero-day exploited in attacks this year. A zero-day is a flaw that attackers are already using before, or as, a fix becomes available.

BleepingComputer lists the earlier exploited Chrome zero-days of 2026 as CVE-2026-2441 in mid-February, CVE-2026-3909 and CVE-2026-3910 in March, CVE-2026-5281 in April, CVE-2026-11645 in June, and CVE-2026-87491 and CVE-2026-85046 in September. The pattern shows that browser emergency updates are now a regular event, not a rare one, and that a monthly patch cycle is too slow for browsers.

Why it matters

The browser is where staff read email links, use cloud systems and log in to banking. A flaw that can be triggered from web content is a convenient entry point, and Google confirming real-world exploitation means attackers are already using it.

The fix does not protect anyone until it is installed. BleepingComputer notes that Chrome can download an update automatically but applies it after the next launch, and that Google said the rollout could take days or weeks to reach all users. Staff who leave Chrome open for weeks, which is common on office PCs and shared machines, can stay on a vulnerable version long after the patch exists.

It is also still unclear who is being targeted and how. When the details are limited, the safe assumption is that any unpatched browser is exposed.

For a small or medium business, the practical risk is a single unpatched laptop. If one staff member's browser is compromised, the attacker may reach saved sessions, cloud accounts and internal web systems that person can open. That is why the update needs to reach every device, including home-office laptops and personal devices used for work, and not only the machines the IT team manages directly.

What businesses can do

  • Check the version. In Chrome, open the menu, go to Help, then About Google Chrome. This triggers an update check. The version should be 157.0.8103.50 or newer.
  • Restart the browser. Ask staff to relaunch Chrome today. A pending update does nothing until the restart happens.
  • Look beyond Chrome. Other Chromium-based browsers share Chrome's engine. Neither source gives advice for them, so check each vendor's own release notes and update them too.
  • Use central management if you have it. If your devices are managed, push the update and set a restart deadline instead of relying on each person.
  • Keep an inventory. List which browsers and versions are installed across laptops, desktops and servers used for browsing. You cannot patch what you do not know about.
  • Stay alert to phishing. Until patching is confirmed, remind staff not to open unexpected links or attachments.

A short written routine helps. Decide who checks browser versions, how often, and what the deadline is for a restart once Google marks a fix as security related. Even a five-minute weekly check beats waiting for a notice.

This story is still developing. Google has released few details, so check Chrome's official release notes for any later builds.

Sources

Keeping browsers, servers and business systems patched across a whole team is routine work that is easy to miss. If you would like help with update management or the systems your staff rely on, see our servers and cloud service or ask for a free consultation.

Ready to talk about your project?

Tell us what you need. We offer a free consultation for your software and IT needs.