Cyber Resilience

CVE-2026-2322

Google Chrome ≤ 145.0.7632.45

Published
11 February 2026
Modified
13 February 2026
Patch / advisory
CVSS Score v3.1 5.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
EPSS Score 0.0023 14th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-2322 is a medium-severity User Interface (UI) Misrepresentation of Critical Information (CWE-451) vulnerability in Google Chrome. Its CVSS base score is 5.4 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Drive-by Compromise (T1189); ranked at the 14th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-2 (Flaw Remediation) and CM-7 (Least Functionality) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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)

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
T1204.001 Malicious Link Execution
An adversary may rely upon a user clicking a malicious link in order to gain execution.
Why these techniques?

UI spoofing via crafted HTML enables drive-by compromise and malicious link execution by tricking users into unintended gestures.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-0907Same product: Apple Macos
CVE-2026-14144Same product: Apple Macos
CVE-2026-5906Same product: Apple Macos
CVE-2026-2318Same product: Apple Macos
CVE-2026-3927Same product: Apple Macos
CVE-2026-2316Same product: Apple Macos
CVE-2026-11300Same product: Apple Macos
CVE-2026-11294Same product: Apple Macos
CVE-2026-3937Same product: Apple Macos
CVE-2026-5898Same product: Apple Macos

Affected Assets

google
chrome
≤ 145.0.7632.45

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires patching the vulnerable Chrome version to eliminate the file-input UI spoofing flaw.

prevent

Restricts browser functionality (e.g., file-input handling or unneeded HTML/JS features) to reduce the attack surface for crafted pages.

SC-18 Mobile Code partial match
prevent

Establishes usage restrictions and controls on mobile code (HTML/JS) that can be abused to perform UI spoofing via file inputs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly address design and implementation of accurate, non-spoofable UI elements.

PR.AT-01 partial match
prevents

User awareness training helps people recognize and avoid harm from UI misrepresentation such as phishing, but does not prevent the flaw itself.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Security testing can detect UI misrepresentation vulnerabilities before deployment.

prevents

Security awareness training can teach users to recognize UI misrepresentation and phishing attempts.

mitigates

Web filtering can block known phishing sites that exploit UI misrepresentation.

prevents

Secure development lifecycle includes UI/UX security requirements that can prevent misrepresentation of critical information.

prevents

Application security requirements can mandate proper display and validation of critical information in the UI.

prevents

Secure coding practices can prevent UI flaws that obscure or spoof critical information.

References