Google has issued an emergency security update for its Chrome web browser to address a high-severity zero-day vulnerability tracked as CVE-2026-11645. The flaw, an out-of-bounds memory access issue in the V8 JavaScript engine, is confirmed to be actively exploited in the wild. Successful exploitation allows a remote attacker to execute arbitrary code within the browser's sandbox by persuading a user to visit a malicious website. This marks the fifth Chrome zero-day patch released in 2026, highlighting a persistent trend of attackers targeting browser vulnerabilities. All Chrome users on Windows, macOS, and Linux are strongly advised to update to the latest version immediately to protect against ongoing attacks.
CVE-2026-11645 is classified as an out-of-bounds memory access vulnerability within V8, Chrome's open-source JavaScript and WebAssembly engine. This type of flaw allows an attacker to read or write to memory outside of the intended buffer. By crafting a malicious HTML page with specific JavaScript code, an attacker can trigger this condition.
Exploitation can lead to heap corruption, which can be leveraged to bypass security mechanisms and achieve arbitrary code execution within the context of the browser's sandboxed renderer process. While the sandbox provides a layer of protection, attackers often chain such exploits with a second vulnerability (a sandbox escape) to gain full control over the underlying system.
Google has explicitly stated, "Google is aware that an exploit for CVE-2026-11645 exists in the wild." This confirms that threat actors are actively using this vulnerability in real-world attacks. As is typical, Google has not released technical details about the exploit or the identity of the attackers to prevent wider abuse and give users time to patch. The vulnerability was responsibly disclosed by a researcher on April 27, 2026.
This is the fifth Chrome zero-day patched in 2026, indicating a sustained focus by threat actors on browser-based exploits for initial access and malware delivery.
A successful exploit of CVE-2026-11645 could allow an attacker to execute arbitrary code on a victim's machine. This could be used to:
Given that the web browser is a primary interface to the internet for most users, a vulnerability like this has a massive potential attack surface, affecting millions of individuals and organizations worldwide.
No specific Indicators of Compromise (IPs, domains, hashes) were provided in the source articles.
The following patterns may help identify systems at risk or potential exploitation activity:
chrome.exe < 149.0.7827.103chrome.exechrome.exe processes spawning suspicious child processes (e.g., powershell.exe, cmd.exe) which could indicate a successful sandbox escape.Detection focuses on identifying vulnerable software and anomalous browser behavior.
chrome.exe spawns a command shell or other unexpected processes. This can be achieved via D3-PA: Process Analysis.Patching is the primary and most effective mitigation.
Help > About Google Chrome.Applying the latest security update from Google is the primary and most effective way to mitigate this vulnerability.
Using web filters and DNS security to block access to malicious or untrusted websites can prevent users from reaching the crafted HTML page needed to trigger the exploit.
Chrome's built-in sandboxing and site isolation are crucial defenses that contain the exploit within the browser process, preventing it from directly accessing the underlying operating system.
The immediate and mandatory action for all organizations is to enforce the update of Google Chrome to the patched version (149.0.7827.103+). This should be managed through centralized endpoint management tools to ensure 100% compliance across all corporate devices. For unmanaged devices (BYOD), organizations should communicate the urgency of this update to all employees. Given that this is the fifth actively exploited zero-day in Chrome this year, organizations must treat browser patching with the same urgency as server-side vulnerabilities. Automating browser updates and conducting regular compliance scans is essential to reduce the window of exposure for future browser-based threats.
As a defense-in-depth measure, EDR solutions should be configured to monitor and alert on suspicious process chains originating from chrome.exe. A common pattern for browser exploits is to trigger the download and execution of a secondary payload. Therefore, rules should be created to detect chrome.exe spawning processes like cmd.exe, powershell.exe, wscript.exe, or mshta.exe. Baselining normal browser behavior is key. While some legitimate applications might use custom protocol handlers that cause such spawns, they are generally rare. An alert on this behavior could be the first indicator of a successful browser compromise and sandbox escape, allowing security teams to intervene before further damage occurs.
CVE-2026-11645 was responsibly disclosed to Google.
Google releases an emergency security update for Chrome to patch CVE-2026-11645.

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.
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.