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-2313: Use after free in Google Chrome

0
High
VulnerabilityCVE-2026-2313cvecve-2026-2313
Published: Wed Feb 11 2026 (02/11/2026, 18:08:01 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Chrome

Description

Use after free in CSS in Google Chrome prior to 145.0.7632.45 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 08:47:06 UTC

Technical Analysis

CVE-2026-2313 is a use-after-free vulnerability identified in the CSS processing component of Google Chrome versions prior to 145.0.7632.45. Use-after-free bugs occur when a program continues to use memory after it has been freed, leading to undefined behavior such as heap corruption. In this case, the vulnerability arises from improper handling of CSS objects, which can be manipulated by an attacker through a crafted HTML page. When a user visits such a malicious page, the attacker can trigger the use-after-free condition, corrupting the heap memory and potentially executing arbitrary code within the context of the browser. This can lead to a full compromise of the browser process, allowing theft of sensitive data, installation of malware, or further network pivoting. The vulnerability requires no privileges and no prior authentication but does require user interaction (visiting a malicious site). The CVSS v3.1 score of 8.8 reflects the high impact on confidentiality, integrity, and availability, combined with ease of exploitation over the network. Although no public exploits are currently known, the vulnerability is classified as high severity by Chromium security. The patch for this vulnerability is included in Chrome version 145.0.7632.45, and users should upgrade immediately to mitigate risk.

Potential Impact

The impact of CVE-2026-2313 is significant for organizations worldwide due to the widespread use of Google Chrome as a primary web browser. Successful exploitation can lead to arbitrary code execution within the browser context, enabling attackers to steal sensitive information such as credentials, session tokens, and confidential data accessed through the browser. It can also serve as a foothold for further attacks within an organization's network, including lateral movement and deployment of malware. The vulnerability compromises confidentiality, integrity, and availability of affected systems. Since exploitation requires only user interaction (visiting a malicious webpage), phishing campaigns or malicious advertisements could be effective vectors. Organizations with employees who frequently browse the internet, especially those in sectors like finance, government, healthcare, and critical infrastructure, face elevated risks. The lack of known exploits in the wild currently reduces immediate threat but does not eliminate the risk of future exploitation, especially given the high severity and ease of exploitation.

Mitigation Recommendations

1. Immediate patching: Organizations must ensure all Google Chrome installations are updated to version 145.0.7632.45 or later to remediate the vulnerability. 2. Browser hardening: Employ browser security features such as sandboxing, site isolation, and strict content security policies to limit the impact of potential exploitation. 3. User awareness: Educate users about the risks of visiting untrusted websites and clicking on suspicious links to reduce the likelihood of triggering the vulnerability. 4. Network defenses: Deploy web filtering and intrusion prevention systems to block access to known malicious sites and detect exploit attempts targeting browser vulnerabilities. 5. Monitoring and response: Implement endpoint detection and response (EDR) solutions to identify anomalous browser behavior indicative of exploitation attempts, such as unusual memory usage or process crashes. 6. Restrict browser extensions: Limit or monitor the use of third-party browser extensions that could increase attack surface or facilitate exploitation. 7. Incident readiness: Prepare incident response plans specifically addressing browser compromise scenarios to enable rapid containment and remediation if exploitation occurs.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Chrome
Date Reserved
2026-02-10T21:51:41.761Z
Cvss Version
null
State
PUBLISHED

Threat ID: 698cce794b57a58fa1b3e2a1

Added to database: 2/11/2026, 6:46:17 PM

Last enriched: 2/27/2026, 8:47:06 AM

Last updated: 4/4/2026, 2:50:24 PM

Views: 248

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 for AI refresh and higher limits.

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

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses