Chrome 0-Day CVE-2026-2441 Exploited in the Wild


Google patched a critical zero-day vulnerability in Chrome on February 13, 2026. The flaw, tracked as CVE-2026-2441, is a use-after-free error in the browser’s CSS handling. Independent researcher Shaheen Fazim reported it on February 11, 2026.

Attackers actively exploit this vulnerability. Google confirmed real-world attacks in its Stable Channel Update. The company urges all users to update immediately to block remote code execution risks.

Unpatched Chrome versions face serious threats. Malicious websites can trigger the memory corruption bug. Attackers gain arbitrary code execution through crafted CSS content.

Vulnerability Details

Use-after-free bugs happen when code accesses memory after it gets freed. Chrome’s CSS engine fails to manage object lifecycles properly in this case. Attackers chain the flaw with sandbox escapes for full system compromise.

Google limited technical details until most users patch. This follows standard policy for exploited zero-days. The vulnerability affects Windows, macOS, and Linux versions.

No public exploits exist yet. Threat actors likely spread attacks through phishing links or hacked sites. Nation-state groups and cybercriminals target browsers for high-value victims.

Official Patch Status

CVE IDCVSS ScoreDescriptionStatus
CVE-2026-2441High (8.8)Use-after-free in CSSActively Exploited nvd.nist​

Patched Versions

PlatformFixed Versions
Windows145.0.7632.75/.76
macOS145.0.7632.75/.76
Linux144.0.7559.75

Chrome rolls out updates gradually. Auto-updates run by default. Users should manually check via Help > About Google Chrome for high-risk systems.

Update Instructions

  • Open Chrome and go to three-dot menu.
  • Select Help > About Google Chrome.
  • Browser checks and installs updates automatically.
  • Restart Chrome to apply patches fully.
  • Enterprises use management tools for mass deployment.

Risks and Impacts

Attackers execute code inside Chrome’s sandbox. They escape to steal data or install malware. Financial sites, email, and corporate tools become prime targets.

Organizations see increased credential theft. Lateral movement follows initial compromise. Government agencies added this to Known Exploited Vulnerabilities lists.

CSS vulnerabilities recur in Chrome history. Rendering engines remain prime attack surfaces. Google invests heavily in fuzzing and bounties to counter threats.

  • Update Chrome across all endpoints immediately.
  • Scan networks for unusual traffic to exploit domains.
  • Block unpatched versions at firewalls.
  • Monitor CISA KEV catalog for federal mandates.
  • Train users to avoid suspicious links.

Google’s Chrome Releases blog provides ongoing details. See the official advisory at Chrome Stable Channel Update.

FAQ

What is CVE-2026-2441?

A use-after-free flaw in Chrome’s CSS engine enabling remote code execution.

Are exploits public?

No public PoCs exist. Google restricts details during active exploitation.

Which platforms are affected?

Windows, macOS, Linux Chrome versions before listed patches.

How do I check my Chrome version?

Go to chrome://version/ or Help > About.

What if auto-update fails?

Download from google.com/chrome and reinstall manually.

Readers help support VPNCentral. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help VPNCentral sustain the editorial team Read more

User forum

0 messages