Latest briefing

Google Chrome XML flaw exploited to execute arbitrary code via CVE-2026-125350

TL;DR

Google has released a patch for CVE-2026-125350, a high-severity use-after-free vulnerability in Chrome's XML component that is currently being exploited in the wild. All Chrome users must update their browsers immediately to prevent potential arbitrary code execution.

What happened

On Monday, Google released updates addressing nine security vulnerabilities. The most critical is CVE-2026-125350, a use-after-free bug located in the XML component. An anonymous researcher discovered and reported the flaw on November 6, 2026.

Google confirmed that an exploit for this vulnerability exists and is being used in real-world attacks. This marks the eighth Chrome zero-day exploited in 2026, following previous vulnerabilities including CVE-2026-2441, CVE-2026-3909, CVE-2026-3910, CVE-2026-5281, CVE-2026-11645, CVE-2026-85046, and CVE-2026-87491.

Why it matters

Use-after-free vulnerabilities occur when a program tries to access memory after it has been freed, which can lead to program crashes, data corruption, or arbitrary code execution. Because an exploit is already active in the wild, attackers can target users by tricking them into visiting malicious sites or processing crafted files. This is a high-priority fix for anyone running a Chromium-based browser.

Who is affected

  • Google Chrome for Windows (versions 157.0.8103.50/.51)
  • Google Chrome for Apple macOS (versions 157.0.8103.50/.51)
  • Google Chrome for Linux (version 157.0.8103.50)
  • Other Chromium-based browsers (including Microsoft Edge, Brave, Opera, and Vivaldi)

What to do now

  1. Update Google Chrome to version 157.0.8103.50/.51 for Windows and macOS, or 157.0.8103.50 for Linux.
  2. Relaunch the browser by navigating to More > Help > About Google Chrome to ensure the update is applied.
  3. Apply updates to all other Chromium-based browsers as soon as their respective patches are released.

What we don't know yet

  • The specific methods used to abuse the exploit in real-world attacks.
  • The identity of the threat actors performing the exploitation.
  • Whether this bug exists in a third-party library used by other software projects.

Sources

  1. thehackernews.comhttps://thehackernews.com/2026/11/google-issues-chrome-security-update.html

Offensive security engineer, ethical hacker and penetration tester. Writes Unpatched Intel from h4rithd.com.