Google has released Chrome version 152 to the stable desktop channel, delivering one of the largest security updates in the browser's history. The update, announced on August 25, 2026, addresses a total of 327 security vulnerabilities. Among these are 10 flaws rated as critical and 61 rated as high-severity. The majority of the critical vulnerabilities are use-after-free memory corruption bugs, which could allow a remote attacker to execute arbitrary code on a user's system. All Chrome users on Windows, macOS, and Linux are urged to apply the update immediately to mitigate the significant security risks.
The Chrome 152 update is a comprehensive security release, patching a wide array of vulnerabilities across numerous browser components. The most severe issues include:
Notable critical vulnerabilities fixed in this release include:
Users can update their browser by navigating to Settings > About Chrome. The browser will automatically check for and download the update.
The vulnerabilities rated critical pose a severe threat. If an attacker successfully exploits one of these flaws, they could execute arbitrary code within the context of the browser. Depending on the browser's permissions, this could lead to:
The attack vector for these types of vulnerabilities is typically a malicious website. An attacker would need to convince a user to visit the site, after which the exploit could be triggered without any further user interaction.
This update is notable for the sheer volume of fixes. Google credited its internal security teams for discovering 299 of the 327 vulnerabilities, highlighting the success of its internal fuzzing and security analysis efforts, which are increasingly augmented by AI. As is standard practice, Google has restricted access to the full technical details of the bugs to give users time to patch. The advisory did not indicate that any of the 327 vulnerabilities were being actively exploited in the wild at the time of release.
CRITICAL. Due to the number and severity of the vulnerabilities fixed, this update should be deployed with the highest priority. All organizations and individual users should ensure their Chrome browsers are updated to version 152.0.7977.64/.65 or later as soon as possible.
Help > About Google Chrome.Relaunch button to apply the update.The following patterns may help identify unpatched systems:
Chrome User-Agent StringAsset Management SystemVulnerability Scanner ResultsThe only effective mitigation is to update Google Chrome to the latest patched version.
Mapped D3FEND Techniques:
Use web filtering to block access to known malicious or untrusted websites that could host exploits.
Mapped D3FEND Techniques:
The primary and most effective countermeasure against the 327 vulnerabilities in Google Chrome is immediate and comprehensive patching. Organizations must enforce policies to ensure all instances of Chrome on desktops and servers are updated to version 152.0.7977.64/.65 or later. This can be achieved through centralized software management tools (e.g., SCCM, Jamf, Intune) that can push the update and force a relaunch of the browser. For unmanaged devices, user communication is key, instructing them to manually check for updates via the 'About Google Chrome' page. Given the critical nature of the use-after-free flaws, this update should be treated as an emergency patch.
Google begins rolling out Chrome 152 to the stable channel for desktop users.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.