Google Scrambles to Patch First Actively Exploited Chrome Zero-Day of 2026

Google Releases Emergency Patch for Actively Exploited Chrome Zero-Day CVE-2026-2441

CRITICAL
February 17, 2026
February 18, 2026
m read
VulnerabilityPatch Management

Related Entities(initial)

Organizations

Google

Products & Tech

BraveChromiumGoogle ChromeMicrosoft EdgeOpera

CVE Identifiers

CVE-2026-2441
HIGH
CVSS:8.8

Full Report(when first published)

Executive Summary

Google has released an emergency security update for its Chrome web browser, addressing the first actively exploited zero-day vulnerability of 2026. The high-severity flaw, tracked as CVE-2026-2441 with a CVSS score of 8.8, is a use-after-free bug in Chrome's Cascading Style Sheets (CSS) component. Google has confirmed it is aware of an exploit for this vulnerability existing in the wild. The patch is available in Chrome version 145.0.7632.75/76 for Windows and macOS. All users should update their browsers immediately to protect against potential attacks.


Vulnerability Details

The vulnerability, CVE-2026-2441, is a use-after-free error within the CSS component of the Chromium engine. This type of memory corruption flaw occurs when a program attempts to use a pointer to a memory location that has already been deallocated (freed). An attacker can exploit this condition to write to arbitrary memory locations, which can lead to a crash or, more critically, arbitrary code execution.

The attack vector requires tricking a user into visiting a specially crafted HTML page. Once the page is loaded, the vulnerability can be triggered without any further user interaction, allowing the attacker to execute code within the context of the browser's sandboxed process.

Affected Systems

  • Google Chrome: Versions prior to 145.0.7632.75/76 for Windows and macOS, and 144.0.7559.75 for Linux.
  • Other Chromium-based Browsers: Browsers such as Microsoft Edge, Brave, and Opera are also likely affected. Users of these browsers should apply updates as soon as they are made available by their respective vendors.

Exploitation Status

Google has explicitly stated that it is "aware that an exploit for CVE-2026-2441 exists in the wild." However, to prevent wider abuse and give users time to patch, the company has not released technical details about the exploit, the threat actors involved, or their targets. This is a standard practice for actively exploited zero-day vulnerabilities.

Impact Assessment

The primary impact of this vulnerability is arbitrary code execution within the browser's sandbox. While the sandbox provides a layer of protection, it is not foolproof. Threat actors often chain a remote code execution vulnerability like this one with a separate sandbox escape vulnerability to achieve a full system compromise. Even without a sandbox escape, an attacker could potentially steal sensitive information stored within the browser, such as cookies, saved passwords, and browsing history, or use the compromised browser process to launch further attacks against internal network resources.

Cyber Observables for Detection

Detecting exploitation of this specific vulnerability without detailed indicators from Google is challenging. However, organizations can hunt for related suspicious activity:

Type Value Description
process_name chrome.exe Monitor for chrome.exe processes that exhibit unusual behavior, such as spawning command shells (cmd.exe, powershell.exe) or making unexpected network connections.
log_source EDR / Endpoint Telemetry Analyze endpoint logs for signs of memory corruption or crashes related to the Chrome browser process, which could indicate exploitation attempts.
command_line_pattern chrome.exe --version Use asset management or scripting to identify endpoints running vulnerable versions of Chrome across the enterprise.

Detection Methods

  • Version Scanning: The most reliable detection method is to identify systems running vulnerable versions of Google Chrome. Use asset inventory tools, vulnerability scanners, or scripts to check the Chrome version on all endpoints.
  • Endpoint Monitoring: Deploy EDR solutions to monitor for suspicious child processes originating from chrome.exe. A browser should not be launching powershell.exe or writing executable files to disk. Reference D3FEND technique D3-PA - Process Analysis.
  • Network Analysis: While the initial exploit is likely delivered over HTTPS, monitoring for connections to known malicious domains or unusual patterns of traffic from browser processes can sometimes indicate a compromise. Reference D3FEND technique D3-NTA - Network Traffic Analysis.

Remediation Steps

  1. Update Immediately: The primary and most urgent remediation step is to update Google Chrome to the latest version (145.0.7632.75/76 or newer for Win/Mac, 144.0.7559.75 or newer for Linux). Chrome's built-in updater will typically handle this automatically, but a browser restart is required to apply the update. Users can manually check for updates by navigating to chrome://settings/help.
  2. Verify Update: After updating, ensure the browser has been restarted to finalize the patch application.
  3. Patch Other Browsers: Users of other Chromium-based browsers should be on high alert for updates from their respective vendors and apply them as soon as they become available.
  4. User Awareness: Remind users to be cautious about clicking links from unknown or untrusted sources, as social engineering is the first step in this attack chain. Reference D3FEND hardening technique D3-ACH - Application Configuration Hardening.

Timeline of Events

1
February 11, 2026
Security researcher Shaheen Fazim discovers and reports the vulnerability to Google.
2
February 16, 2026
Google releases an emergency security update for Chrome to patch CVE-2026-2441.
3
February 17, 2026
This article was published

Article Updates

February 18, 2026

Update confirms patch release date of February 13, 2026, for CVE-2026-2441 and explicitly lists Vivaldi and Opera as affected Chromium browsers.

Further details regarding the actively exploited Chrome zero-day, CVE-2026-2441, confirm that the critical patch was released on February 13, 2026. This update also explicitly identifies Vivaldi and Opera as additional Chromium-based browsers impacted by the use-after-free vulnerability, alongside Microsoft Edge and Brave. Remediation efforts continue to emphasize immediate software updates, aligning with the D3FEND technique D3-SU - Software Update, to protect against ongoing exploitation. Users are urged to ensure all Chromium-based browsers are updated and restarted.

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)

Tags

Google Chromebrowser securitychromiumuse-after-freezero-day

📢 Share This Article

Help others stay informed about cybersecurity threats