Chrome 0-Day Vulnerability Actively Exploited by Attackers in the Wild
Google has issued a critical patch for a high-severity zero-day vulnerability in Chrome, following confirmation of active exploitation. The vulnerability, identified as CVE-2026-2441, is categorized as a use-after-free bug within the browser's CSS…
Google has issued a critical patch for a high-severity zero-day vulnerability in Chrome, following confirmation of active exploitation. The vulnerability, identified as CVE-2026-2441, is categorized as a use-after-free bug within the browser's CSS handling. This flaw was reported by independent researcher Shaheen Fazim on Wed, Feb 11, 2026.
Google disclosed this issue in conjunction with the latest Stable channel update, highlighting the existence of an exploit and advising users to upgrade immediately to reduce risk.
Chrome versions prior to the patched releases are susceptible to remote code execution attacks, wherein attackers could exploit memory corruption to execute arbitrary code through malicious web content.
Use-after-free vulnerabilities are often linked to improper object lifecycle management in rendering engines, permitting access to freed memory after deallocation.
The CVE-2026-2441 vulnerability has been weaponized by attackers, potentially combining it with other methods for sandbox escape and privilege escalation on Windows, macOS, and Linux systems. Detailed information about the bug has been restricted by Google until a majority of users have updated, in line with its policy on actively exploited vulnerabilities.
The security update addresses a single high-severity issue in this release cycle.
CVE ID CVSS Score Description
Google has issued a critical patch for a high-severity zero-day vulnerability in Chrome, following confirmation of active exploitation.
CVE-2026-2441 High (TBD) Use after free in CSS
Patched versions have been released as follows:
Platform Patched Versions
Windows 145.0.7632.75/.76
macOS 145.0.7632.75/.76
Linux 144.0.7559.75
Users are advised to apply updates via Chrome's built-in updater or enterprise management tools .
The update rollout is gradual, occurring over several days or weeks. While auto-updates are enabled by default, manual update checks are recommended for high-risk environments.
Organizations should prioritize updating Chrome installations, monitor for indicators of compromise such as unusual network traffic to Google domains, and consult CISA’s Known Exploited Vulnerabilities catalog for federal advisories.
This incident represents another CSS-related zero-day in Chrome's history, highlighting ongoing challenges in rendering engine security amid increasing threats from nation-state and financially driven attacks targeting browsers.
No specific indicators of compromise are public at this time, but threat actors may deploy exploits via phishing or compromised websites. Security teams can refer to the Chrome release log and Chromium security page for further updates.
Based on reporting by Cyber Security News.
