VulnerabilityPublished 11 Feb 2026

CVE-2026-2320: Google Chrome · Inappropriate Implementation

Affects Google ChromeSource CVE Database V5

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

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

6.5Medium

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

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

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

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: 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: None: There is no impact to availability within 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 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

To mitigate CVE-2026-2320, organizations should promptly update all Google Chrome installations to version 145.0.7632.45 or later, where the vulnerability is fixed. In environments where immediate patching is not feasible, administrators can consider deploying browser policies to restrict or disable file input interactions on untrusted or high-risk websites, reducing the attack surface. User education is critical; training users to recognize suspicious UI behavior and avoid interacting with unexpected file input prompts can lower exploitation likelihood. Employing browser security extensions that detect or block UI spoofing attempts may provide additional protection. Network-level defenses such as web filtering and URL reputation services can help prevent access to malicious sites hosting crafted HTML pages. Monitoring browser logs for unusual UI interaction patterns could aid in early detection of exploitation attempts. Finally, organizations should maintain an up-to-date inventory of Chrome versions in use and enforce update policies to minimize exposure duration.

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: Medium)

Impact

The primary impact of CVE-2026-2320 is on the integrity of user interactions within Google Chrome. By enabling UI spoofing, attackers can deceive users into believing they are interacting with legitimate browser UI elements or trusted websites, potentially leading to phishing, credential theft, or unauthorized actions. Although confidentiality and availability are not directly affected, the integrity compromise can have cascading effects, such as enabling further attacks or data compromise through social engineering. Organizations relying heavily on Chrome for web access, especially those with users less trained in security awareness, may face increased risk of targeted phishing campaigns exploiting this vulnerability. Since exploitation requires user interaction, the threat is mitigated somewhat by user vigilance but remains significant in environments where users frequently handle untrusted web content. The lack of known exploits reduces immediate risk but does not eliminate the potential for future attacks once exploit code becomes available. Enterprises with large user bases on Chrome versions prior to 145.0.7632.45 should prioritize patching to prevent exploitation. The vulnerability could be leveraged in targeted attacks against sectors such as finance, government, and critical infrastructure where trust in UI elements is crucial.

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:11 UTC

WeaknessesCWE-451

Technical details

References

Community reviews

Related threats