Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-2441: Use after free in Google Chrome

0
High
VulnerabilityCVE-2026-2441cvecve-2026-2441
Published: Fri Feb 13 2026 (02/13/2026, 18:27:48 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Chrome

Description

Use after free in CSS in Google Chrome prior to 145.0.7632.75 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

AI-Powered Analysis

AILast updated: 02/13/2026, 19:03:58 UTC

Technical Analysis

CVE-2026-2441 is a use-after-free vulnerability identified in the CSS processing component of Google Chrome prior to version 145.0.7632.75. Use-after-free vulnerabilities occur when a program continues to use a pointer after the memory it points to has been freed, leading to undefined behavior including potential arbitrary code execution. In this case, the vulnerability can be triggered remotely by an attacker who crafts a malicious HTML page that exploits the flaw in Chrome's CSS handling. When a user visits such a page, the attacker can execute arbitrary code inside Chrome's sandbox environment. Although sandboxing limits the attacker's capabilities, successful exploitation can still lead to significant compromise of the browser environment, potentially enabling further attacks on the host system or data leakage. The vulnerability does not require user authentication or interaction beyond visiting the malicious page, increasing its risk profile. No public exploits have been reported yet, but the Chromium security team has classified this vulnerability as high severity, indicating a serious threat. The vulnerability affects all Chrome users running versions prior to 145.0.7632.75, which is a widely deployed browser globally and across Europe. The lack of a CVSS score means severity assessment must consider the potential impact on confidentiality, integrity, and availability, the ease of exploitation, and the scope of affected systems.

Potential Impact

For European organizations, the impact of CVE-2026-2441 can be significant. Google Chrome is the dominant web browser in Europe, used extensively in both private and public sectors. Exploitation could lead to arbitrary code execution within the browser sandbox, potentially allowing attackers to steal sensitive information, manipulate web sessions, or pivot to internal networks. This is especially critical for organizations handling sensitive personal data under GDPR regulations, as breaches could lead to severe legal and financial consequences. The vulnerability's remote exploitation capability without user authentication or complex interaction increases the risk of widespread attacks, including targeted campaigns against high-value targets such as government agencies, financial institutions, and critical infrastructure operators. Additionally, the sandboxed environment may limit but not eliminate the risk of full system compromise, particularly if combined with other vulnerabilities. The absence of known exploits in the wild provides a window for proactive patching, but the high severity rating necessitates urgent attention.

Mitigation Recommendations

To mitigate CVE-2026-2441, European organizations should immediately update all Google Chrome installations to version 145.0.7632.75 or later, where the vulnerability is patched. Organizations should enforce automated update policies to ensure browsers remain current. Network-level defenses such as web filtering and intrusion detection systems should be configured to block or monitor access to suspicious or untrusted websites that could host malicious HTML content. Security teams should conduct targeted user awareness campaigns to inform about the risks of visiting untrusted sites. Additionally, deploying endpoint detection and response (EDR) solutions can help detect anomalous browser behavior indicative of exploitation attempts. For high-security environments, consider restricting browser usage to managed and monitored instances with strict content security policies. Regular vulnerability scanning and penetration testing should include checks for outdated browser versions. Finally, organizations should monitor threat intelligence feeds for any emerging exploit activity related to this vulnerability.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Chrome
Date Reserved
2026-02-13T00:00:18.713Z
Cvss Version
null
State
PUBLISHED

Threat ID: 698f723cc9e1ff5ad857abe3

Added to database: 2/13/2026, 6:49:32 PM

Last enriched: 2/13/2026, 7:03:58 PM

Last updated: 2/13/2026, 7:53:41 PM

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats