Google Patches Actively Exploited High-Severity Chrome Zero-Day (CVE-2026-11645)

Google Patches Fifth Actively Exploited Chrome Zero-Day of 2026

HIGH
June 9, 2026
June 14, 2026
m read
VulnerabilityPatch Management

Related Entities(initial)

Organizations

Google

Products & Tech

BraveGoogle ChromeMicrosoft EdgeV8 JavaScript engineVivaldi

CVE Identifiers

CVE-2026-11645
HIGH
CVSS:8.8

Full Report(when first published)

Executive Summary

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.


Vulnerability Details

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.

  • CVSS Score: 8.8 (High)
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: Required (User must navigate to a malicious page)

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.

Affected Systems

  • Google Chrome versions prior to 149.0.7827.103 for Windows and macOS.
  • Google Chrome versions prior to 149.0.7827.102 for Linux.
  • Other Chromium-based browsers such as Microsoft Edge, Brave, Opera, and Vivaldi are also likely affected and will require updates from their respective vendors.

Exploitation Status

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.

Impact Assessment

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:

  • Install spyware to steal credentials, financial information, and other sensitive data.
  • Deploy ransomware to encrypt the user's files.
  • Use the compromised machine as part of a botnet.
  • Gain an initial foothold in a corporate network, from which to launch further attacks.

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.

IOCs — Directly from Articles

No specific Indicators of Compromise (IPs, domains, hashes) were provided in the source articles.

Cyber Observables — Hunting Hints

The following patterns may help identify systems at risk or potential exploitation activity:

Type
File Version
Value
chrome.exe < 149.0.7827.103
Description
Use endpoint management tools to query for outdated versions of Google Chrome, which are vulnerable.
Type
Network Traffic Pattern
Value
Suspicious JavaScript downloads
Description
Monitor for connections to newly registered or low-reputation domains serving obfuscated JavaScript. This is a general indicator of web-based threats.
Type
Process Name
Value
chrome.exe
Description
Monitor for chrome.exe processes spawning suspicious child processes (e.g., powershell.exe, cmd.exe) which could indicate a successful sandbox escape.

Detection & Response

Detection focuses on identifying vulnerable software and anomalous browser behavior.

  1. Asset Management: Regularly scan all endpoints to ensure that Chrome and other web browsers are updated to the latest patched versions. Use EDR or asset inventory systems to flag non-compliant devices.
  2. Endpoint Detection and Response (EDR): Configure EDR policies to monitor for suspicious process chains originating from browsers. An alert should be triggered if chrome.exe spawns a command shell or other unexpected processes. This can be achieved via D3-PA: Process Analysis.
  3. Network Security: Employ web filtering and DNS security to block access to known malicious websites and domains. While this may not block a zero-day attack from a new source, it is a critical layer of defense against common threats.

Mitigation

Patching is the primary and most effective mitigation.

  1. Update Immediately: All users and administrators must ensure that Google Chrome is updated to version 149.0.7827.103 or later on Windows/macOS and 149.0.7827.102 or later on Linux. Chrome's built-in auto-update feature should handle this, but users can force an update by navigating to Help > About Google Chrome.
  2. Patch Chromium Browsers: Users of other Chromium-based browsers should monitor for and apply updates from their vendors as soon as they become available.
  3. Principle of Least Privilege: Ensure users do not operate with local administrator privileges for daily tasks. This can limit the impact of a successful exploit, preventing system-wide changes.
  4. Enable Site Isolation: Ensure Chrome's Site Isolation feature is enabled, as it provides an additional layer of security by separating the processes of different websites.

Timeline of Events

1
April 27, 2026
CVE-2026-11645 was responsibly disclosed to Google.
2
June 8, 2026
Google releases an emergency security update for Chrome to patch CVE-2026-11645.
3
June 9, 2026
This article was published

Article Updates

June 10, 2026

Severity increased

CISA has added the actively exploited Chrome zero-day (CVE-2026-11645) to its KEV catalog, mandating federal agencies to patch by July 1, 2026, highlighting increased urgency.

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has officially recognized the active exploitation of CVE-2026-11645, the Google Chrome V8 zero-day, by adding it to its Known Exploited Vulnerabilities (KEV) catalog. This inclusion mandates all U.S. Federal Civilian Executive Branch agencies to apply patches for this vulnerability by July 1, 2026. This development significantly elevates the urgency and priority for all organizations, not just federal ones, to remediate this flaw immediately due to confirmed ongoing attacks and its critical impact potential. The KEV listing serves as a clear signal of the severe and present danger posed by this vulnerability.

June 14, 2026

Google's urgent Chrome update patches 28 vulnerabilities, including the actively exploited CVE-2026-11645, now confirmed as a drive-by compromise attack vector.

The latest Chrome update, version 149, addresses a total of 28 vulnerabilities, significantly expanding beyond the previously reported CVE-2026-11645. Google has now confirmed that CVE-2026-11645 is being actively exploited via 'drive-by compromise' attacks, where users are compromised simply by visiting a malicious website. This type of zero-day is highly valued by sophisticated threat actors, including state-sponsored APT groups like APT28 and APT29, as well as cybercriminal organizations. Enhanced detection methods, such as monitoring EDR alerts for suspicious process creation from chrome.exe and network traffic analysis for unusual C2 communications, are now emphasized.

Timeline of Events

1
April 27, 2026

CVE-2026-11645 was responsibly disclosed to Google.

2
June 8, 2026

Google releases an emergency security update for Chrome to patch CVE-2026-11645.

Sources & References(when first published)

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

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.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Editorial Standards & Analyst Review

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.

Tags

Browser SecurityGoogle ChromePatch ManagementRemote Code ExecutionV8 EngineZero-Day

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

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.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

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 Generator

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.