Anyone using Google’s Chrome web browser should promptly install the available update and restart the browser. The update fixes several high-risk security vulnerabilities, one of which is already being exploited online.
In its release announcement, Google lists nine security vulnerabilities fixed by the update. Attackers are targeting a use-after-free vulnerability in XML, in which resources are used after they have already been freed. This results in undefined memory contents and usually causes the software to crash, but it can also lead to the execution of injected malicious code. Simply viewing carefully crafted webpages is generally enough to trigger it, which is why Google rates the severity as “high” (CVE-2026-125350). Six other vulnerabilities are rated high risk, and two more are rated medium risk.
Google fixes the issues in Chrome versions 157.0.8103.50 for Android and Linux and 157.0.8103.50/.51 for macOS and Windows. Google is rolling out the updates gradually over the coming days and weeks. Extended Stable should be updated to Chrome version 156.0.8078.96 . This version for macOS and Windows fixes 11 security vulnerabilities, including the one already being exploited.
You can install the update through the browser’s version dialog, which is in the settings under “Help” – “ Google Chrome.” Because the vulnerabilities affect the Chromium base, other browsers based on it, such as Microsoft Edge and Brave, are also likely to release security updates soon. Microsoft has already said it is working on a security fix for Edge. Users of these browsers should therefore also check for updates through the respective version dialog. On Android and iOS, the respective app stores handle update distribution. As a result, some devices receive the update considerably later. On Linux, the software manager for the distribution in use is generally responsible for delivering the update.
Earlier, at the beginning of September, Google had fixed an exploited security vulnerability in Chrome . It was a type confusion vulnerability in the V8 JavaScript engine.
This article was originally published in German . It was translated with technical assistance and editorially reviewed before publication.
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
