VulnerabilityPublished 11 Feb 2026Updated 26 Feb 2026

CVE-2026-2321: Google Chrome · Use After Free

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 8.8 High : upgrade to 145.0.7632.45 soon.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score

8.8High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 145.0.7632.45

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Google Chrome to 145.0.7632.45.

Affected software

Product	Affected	Fixed in
GoogleChrome	Affected >=145.0.7632.45 <145.0.7632.45	Fixed in 145.0.7632.45

AI-suggested

Immediate update to Google Chrome version 145.0.7632.45 or later, where the vulnerability is patched.
Implement enterprise-wide browser update policies to ensure timely deployment of security patches.
Educate users about the risks of interacting with untrusted web content and suspicious UI elements to reduce the likelihood of triggering the exploit.
Employ browser hardening techniques such as enabling site isolation, sandboxing, and strict content security policies to limit the impact of potential exploitation.
Monitor network traffic and endpoint behavior for anomalies indicative of exploitation attempts, including unusual browser crashes or memory corruption signs.
Use endpoint detection and response (EDR) tools to detect and respond to suspicious activities related to browser processes.
Consider restricting access to high-risk websites or implementing web filtering solutions to reduce exposure to malicious pages.
Maintain regular backups and incident response plans to mitigate damage in case of successful exploitation.

Description

Use after free in Ozone in Google Chrome prior to 145.0.7632.45 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Medium)

Impact

The impact of CVE-2026-2321 is significant due to its potential to allow remote code execution within the browser context, leading to full compromise of user data confidentiality, integrity, and system availability. Attackers can exploit this vulnerability to execute arbitrary code, install malware, steal sensitive information, or pivot to other parts of the network. Given Chrome's dominant market share globally, a successful exploit could affect millions of users and organizations. Enterprises relying on Chrome for daily operations, especially those handling sensitive or classified information, face increased risk of data breaches and operational disruption. The requirement for user interaction slightly reduces the attack surface but does not eliminate risk, as social engineering or drive-by attacks can induce the necessary UI gestures. The absence of known exploits in the wild currently limits immediate threat but does not preclude future exploitation, especially as threat actors analyze the vulnerability post-disclosure.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 08:48 UTC

Technical details

References

Community reviews

Related threats