Mastodon Mastodon Mastodon Mastodon

Google fixes eighth Chrome zero-day vulnerability — use-after-free in XML component

Photo of author

CyberSecureFox Editorial Team

Published:

Google Chrome has received an emergency update that closes the zero-day vulnerability CVE-2026-125350 — a use-after-free bug in the browser’s XML component which, according to Google, is already being exploited in real-world attacks. The vulnerability affects all Chrome versions prior to 157.0.8103.50 on Windows, macOS, and Linux. Users must update their browser immediately: CISA has added this vulnerability to the KEV catalog with a remediation deadline of November 24, 2026. We have already written about this vulnerability earlier — now we are adding new details to complete the picture.

Technical details of the vulnerability

According to the CVE record, the vulnerability is classified as CWE-416 (Use After Free) and has received a Chromium severity rating of High. The crux of the issue is access to a memory area after it has been freed: the program retains a pointer to an object that has already been deleted, and on subsequent access an attacker can substitute the contents of that memory. In the case of CVE-2026-125350, the vulnerable component is the browser’s XML parser.

The attack vector is remote: according to the CVE record, an attacker can execute arbitrary code inside the browser sandbox via a specially crafted HTML page. This means that to exploit the vulnerability it is enough to lure the victim to a malicious web resource — no interaction with the file system or installation of additional software is required.

It is worth noting a discrepancy in the discovery attribution. The initial news item stated that the issue was discovered by an anonymous researcher on November 6, 2026. However, the Google security bulletin lists two researchers: Arni Hardarson of Neonix Security, who reported the issue on October 12, 2026, and an anonymous researcher who submitted a report on November 6. Thus, the vulnerability was known to Google for at least a month before the patch was released.

Update and affected versions

The patch was included in an update containing nine security fixes. The fixed versions depend on the platform:

  • Windows and macOS: 157.0.8103.50 / 157.0.8103.51
  • Linux: 157.0.8103.50

All Chrome versions below 157.0.8103.50 are considered vulnerable. The update is being rolled out gradually, but it can be installed manually via the “Help” → “About Google Chrome” menu.

Eight zero-days in a year: the 2026 timeline

CVE-2026-125350 has become the eighth actively exploited zero-day vulnerability in Chrome in 2026 — this count is based on Google security bulletins, each of which confirmed the presence of an exploit “in the wild.” The seven preceding vulnerabilities affect various browser components:

All eight vulnerabilities have been added to the CISA KEV catalog. We have previously analyzed the sixth vulnerability in this series and the fifth in detail in earlier articles.

A notable detail: five out of eight vulnerabilities in 2026 are related to the V8 engine or the graphics stack, whereas CVE-2026-125350 affects the XML parser — a component that appears less frequently in Chrome zero-day exploitation. This may indicate that attackers are expanding the attack surface they are researching.

Impact assessment

Chrome remains the most widespread desktop browser, so every confirmed zero-day potentially affects billions of devices. Arbitrary code execution inside the sandbox is a serious, though not maximal, threat level: for full system compromise the attacker would additionally need a sandbox escape. Nevertheless, even code execution in the renderer context allows theft of data from the current browser session, interception of credentials, and redirecting the user.

For now, Google is not disclosing details of real-world attacks: the threat actors behind the exploitation, the targeted industries, and indicators of compromise all remain unknown. Such lack of detail is typical for Chrome zero-days — technical information is only published after the patch has been widely deployed.

Recommendations

  • Update Chrome immediately to version 157.0.8103.50 or later on all platforms. Check your current version via “Help” → “About Google Chrome.”
  • For organizations: given the CISA KEV status, U.S. federal agencies are required to remediate the vulnerability by November 24, 2026. Commercial organizations are advised to follow a similar timeline.
  • Check Chromium-based browsers: since the vulnerability resides in the Chromium XML component, it may affect other browsers using this engine — Microsoft Edge, Brave, Opera. Monitor updates for these products.
  • Enable automatic updates for Chrome if they are disabled, and restart the browser after installing the patch — the update is only applied after a restart.

Eight zero-days in less than a full year of 2026, while for the whole of 2025, according to the original report, there were just as many, is a signal that the pace of discovering and exploiting vulnerabilities in Chrome is not slowing down. The only reliable protection is to keep the browser up to date and apply patches on the day they are released, especially when there is confirmed exploitation in real-world attacks.


CyberSecureFox Editorial Team

The CyberSecureFox Editorial Team covers cybersecurity news, vulnerabilities, malware campaigns, ransomware activity, AI security, cloud security, and vendor security advisories. Articles are prepared using official advisories, CVE/NVD data, CISA alerts, vendor publications, and public research reports. Content is reviewed before publication and updated when new information becomes available.

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.