The images in this article were generated with artificial intelligence. How we publish
Google has published security patches for its Chrome browser after identifying a vulnerability that is already being exploited in real environments. The failure, recorded as CVE-2026-2441 and qualified with a high CVSS score (8.8), affects CSS processing and can allow an attacker to run code remotely through a HTML page designed to take advantage of the failure; this technical description is found in the NIST vulnerability database, where more information can be found in detail: NVD - CVE-2026-2441.
The detection was attributed to investigator Shaheen Fazim, who reported the problem on 11 February 2026. Google has publicly confirmed that there is at least one active explosion for this vulnerability, although at the moment the company has not disclosed specific details about how it is being used or who the targets have been. The official update note is available on the Chrome release blog: Chrome Releases - Stable Channel update.

From the technical point of view, it is a classic "use-after-free" related to the engine that interprets the CSS rules. In simple terms, that type of failure arises when the browser tries to use memory that was already released, which can open the door to an attacker manipulating the program's behavior and running code within the restrictions of the running environment. Although the operation is often limited to the "sandbox" of the browser, this does not decrease the gravity: browsers are privileged targets because they are installed on almost all computers and mobile and process external content continuously, so a single failure can affect millions of users.
This emergency intervention makes CVE-2026-2441 the first zero-day actively exploited in Chrome that Google has patched in 2026. It is not an isolated phenomenon: during the previous year the company corrected several critical vulnerabilities in the browser, some of them also exploited in practice. This trend underlines the need to keep the software up to date.
In parallel, in recent weeks Apple also launched patches for multiple systems - including iOS, iPadOS and macOS - to correct a zero- day that had been used in targeted attacks against specific users; Apple described that campaign as "extremely sophisticated" and published general information about its security updates on its support page: Apple - Security Updates. Both incidents remember that vulnerabilities on popular platforms are often exploited by actors with different objectives, from opportunistic cybercriminals to more targeted operations.
If you use Chrome in Windows or macOS, Google recommends installing versions 145.0.7632.75 or 145.0.7632.76; for Linux the version indicated is 144.0.7559.75. To check that you have the latest version simply open the Chrome menu, go to Help and select About Google Chrome; the browser will search for updates and ask to restart (Relaunch) if it applies. You can also follow Google's official instructions to update Chrome here: Update Google Chrome. Updating as soon as possible is the most effective measure to reduce risk.

Users of other Chromium-based browsers, such as Microsoft Edge, Brave, Opera or Vivaldi, should also remain vigilant: these projects share much of the underlying code and it is therefore common for the corrections to reach the other implementations with little delay. If you use any of those browsers, check your supplier's security notes and apply the updates as soon as they are available.
Beyond the spot patch, it is appropriate to remember some good practices: keep the operating system and extensions up to date, limit the permissions of unknown extensions and avoid opening suspicious links or files from unverified sources. The combination of an updated browser and a prudent conduct in navigation significantly reduces the attack surface.
In short, this security notice reveals an already known reality: browsers remain one of the preferred entry doors for attackers. If you use Chrome or any Chromium-based browser, do the update today and keep the habit of regularly reviewing security updates.
Related
More news on the same subject.

Four Plex2Shell CVE allows remote execution and mining and proxy backdoor deployment
In recent days, an increase in attacks has been confirmed that take advantage of a chain of failures in Plex Media Server - nicknamed "Plex2Shell" by researchers - to run code r...

GhostAction Expands Attack: phishing to steal credentials and persistence in VS Code
A group behind the GhostAction campaign - already known for infiltrating GitHub Actions workflows into open source projects - has expanded its arsenal: in addition to installing...

ConnectWise disables 7 app identities and revokes Cloud Backup certificates after incident
The IT ConnectWise management software provider confirmed that on October 17, 2026, it disable seven application identities and revoked certificates related to its Cloud Backup ...

Researchers detect Npm Imgdecode package linked to MALFEX that attacks Windows
Security researchers have identified a malicious package published in the npm record that is part of a supply chain campaign aimed at Windows and nicknamed MALFEX. The package, ...

OpenBSD 7.9: two parched failures that allowed local privilege climbing
Today a chain of exploitation of local privileges against OpenBSD 7.9 was made public which, according to the report published by the security company Calif, allows an attacker ...

OpenAI reveals unaligned IA incidents; a GPT-5.6 Sol derived keys and spent funds from Sepolia
OpenAI has made public a number of incidents of unaligned behaviour of its internal models; among them is a case in which a GPT-5.6 family research model Sol derived private key...