CVE-2026-2322VulnerabilityPublished 11 Feb 2026

CVE-2026-2322: Google Chrome · Inappropriate implementation

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium : upgrade to 145.0.7632.45 when convenient.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

5.4Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% 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:N/I:L/A:L

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

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: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

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 2026-10-26.

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 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

To mitigate CVE-2026-2322, organizations should prioritize updating Google Chrome to version 145.0.7632.45 or later as soon as the patch is available. Until then, users should be educated about the risks of interacting with untrusted websites and performing unexpected UI gestures. Implementing browser security policies that restrict or monitor the use of file input elements on untrusted sites can reduce exposure. Employing web content filtering and URL reputation services can help block access to malicious pages designed to exploit this vulnerability. Additionally, organizations should consider deploying endpoint protection solutions that detect anomalous browser behavior indicative of UI spoofing attempts. Regular security awareness training emphasizing caution with unfamiliar web content and UI prompts will further reduce the likelihood of successful exploitation.

Description

Inappropriate implementation in File input in Google Chrome prior to 145.0.7632.45 allowed a remote attacker who convinced a user to engage in specific UI gestures to perform UI spoofing via a crafted HTML page. (Chromium security severity: Low)

Impact

The primary impact of CVE-2026-2322 is on the integrity and availability of the user interface within affected Chrome browsers. UI spoofing can lead to users being deceived into performing harmful actions such as submitting sensitive data to attackers or executing unintended commands. While confidentiality is not directly compromised, the deceptive UI could facilitate phishing or other social engineering attacks, indirectly risking sensitive information. The requirement for user interaction limits automated exploitation but does not eliminate risk, especially in environments where users may be targeted with crafted web content. Organizations relying heavily on Chrome for web access, especially those with users less trained in security awareness, may face increased risk of fraud or operational disruption. The absence of known exploits reduces immediate threat but does not preclude future exploitation attempts.

CWE-451User Interface (UI) Misrepresentation of Critical Information (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The user interface (UI) does not properly represent critical information to the user, allowing the information - or its source - to be obscured or spoofed. This is often a component in phishing attacks.
Implementation · Input Validation
Perform data validation (e.g. syntax, length, etc.) before interpreting the data.
Architecture and Design · Output Encoding
Create a strategy for presenting information, and plan for how to display unusual characters.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
Attack patterns
Spear Phishing (opens in a new tab)
Mobile Phishing (opens in a new tab)
Phishing (opens in a new tab)
Resource Location Spoofing (opens in a new tab)
Action Spoofing (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Feb 2026, 14:16 UTC

WeaknessesCWE-451

Technical details

References

Community reviews

Related threats