Google Chrome Emergency Security Update for CVE-2025-6558
Google Chrome Emergency Security Update: CVE-2025-6558
π¨ Critical Zero-Day Vulnerability Discovered
Google has released an emergency security update for Chrome 138 to address a critical zero-day vulnerability, CVE-2025-6558, that is actively being exploited in the wild. This flaw impacts the ANGLE and GPU components of the browser.
CVE-2025-6558 was discovered by Google’s Threat Analysis Group and is described as a high-severity vulnerability that can allow attackers to execute arbitrary code on the affected system.
Source: Wikipedia
Google’s internal security researchers, ClΓ©ment Lecigne and Vlad Stolyarov, identified this vulnerability on June 23, 2025. The vulnerability involves incorrect validation of untrusted input, which can potentially allow attackers to execute malicious code on affected systems.
The most concerning aspect of this vulnerability is that it has been actively exploited before a patch was released, which is why it is designated as a "zero-day" vulnerability.
Important: An exploit for CVE-2025-6558 exists in the wild! This means attackers have already used this vulnerability to compromise systems.
⚠️ Emergency Update Released
To mitigate the risk, Google has rolled out an emergency security update across all platforms:
- Chrome version 138.0.7204.157/158 for Windows and Mac
- Chrome version 138.0.7204.157 for Linux
- Android versions of Chrome will receive updates through Google Play over the coming days
This update includes critical fixes to protect users from ongoing attacks and further exploits targeting the identified vulnerability.
Source: Chromium
π Other Security Fixes Included
Beyond addressing the critical CVE-2025-6558 vulnerability, this emergency update also resolves multiple other security flaws identified by Google’s ongoing security research efforts. These fixes help further protect users from potential attacks.
To keep your Chrome browser safe, it is highly recommended to update to the latest version immediately by going to the Chrome Help Center.

Comments