Google has patched CVE-2026-125350, a use-after-free flaw in Chrome's XML component, and confirmed an exploit is already circulating in the wild. CISA set 24 November 2026 as the remediation deadline.
Google patched an actively exploited zero-day in Chrome on 9 November 2026. The flaw, tracked as CVE-2026-125350, is a use-after-free bug in the browser's XML component, and Google has confirmed that an exploit for it is already circulating in the wild.
An anonymous researcher reported the bug on 6 November and the fix shipped just three days later, in Chrome 157.0.8103.50. That same release closes nine security issues in total. According to Qualys, the US cybersecurity agency CISA added the flaw to its Known Exploited Vulnerabilities catalog on 10 November and set 24 November 2026 as the remediation deadline for federal agencies.
Why it matters
Use-after-free bugs let an attacker manipulate memory and potentially run code inside the browser process. With this class of flaw, the victim only has to open a crafted web page — no download, no dialog to approve. The attack surface is a piece of software every single machine in the office opens every day.
CyberInsider reports that the root cause sits in libxslt, the library Chrome uses to transform XML documents with XSLT stylesheets, specifically in its pattern-matching cache. The affected code path only runs on pages that actually use XSLT. CISA, however, noted that browsers sharing the same Chromium base — including Microsoft Edge and Opera — may be affected by the same defect. The exposure is therefore not limited to machines with Chrome installed.
By SecurityWeek's count this is the eighth exploited Chrome zero-day Google has patched in 2026. Most of the earlier ones this year sat in the V8 JavaScript engine; this is the first to land in the XML code.
What this means for businesses in Turkey
At most small and mid-sized companies here, browser updating is effectively left to the end user. Chrome downloads the patch in the background, but the fix does not take effect until the browser is restarted. In offices where machines stay powered on and Chrome stays open for days, the update looks applied while the vulnerable code is still running.
There is a regulatory dimension as well. Article 12 of Turkey's Personal Data Protection Law (KVKK, Law No. 6698) obliges data controllers to secure the personal data they hold. If customer or staff data leaks through a compromised endpoint, the incident must be notified to the Board, and under the fine amounts published by the Authority for 2026, breaches of data security obligations carry administrative fines between TRY 256,357 and TRY 17,092,242. Leaving a publicly patched, actively exploited flaw open for months is difficult to defend in an audit.
What we recommend at Kamer Bilişim
- Inventory your browser versions and force a restart. Check the Chrome version on every device, update anything below 157.0.8103.50, and make sure the browser is actually closed and reopened. An installed update is not a deployed one.
- Centralise browser updates through policy. Use Chrome Enterprise ADMX templates or group policy to enforce updates and schedule relaunches. Where a device cannot be updated right away, disabling XSLT by policy is a reasonable stopgap.
- Make patch tracking part of your maintenance contract. Put a process in place that monitors operating system, browser, server and firewall patches and follows active-exploitation feeds such as the CISA KEV catalog. For a product that produces eight zero-days a year, an annual check-up is not enough.
If you have no central view of whether your endpoints are up to date, get in touch and we can map your current position. We work on site across the Anatolian side of Istanbul and provide remote support elsewhere.
Source: Qualys ThreatPROTECT, CyberInsider, SecurityWeek, KVKK
Source: Qualys ThreatPROTECT