ChromeWeb browser · Google

CVE-2026-2322

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-11

Fix available

A fix is available. Upgrade to 145.0.7632.45 or later.

See remediation →

61/100

Remediation priority · Elevated

Remotely reachable No privileges

Official description

NVD · unedited

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)

Technical summary

dbcve analysis · high confidence

This is a UI spoofing vulnerability in Google Chrome's File input component. A remote attacker could trick users into engaging in specific UI gestures on a crafted HTML page, allowing the attacker to manipulate the user interface. The vulnerability exists in Chrome versions prior to 145.0.7632.45.

MitigationUpdate Google Chrome to version 145.0.7632.45 or later. Organizations should deploy browser updates through their patch management systems to ensure all users receive the fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

ChromeWeb browser

Affected:< 145.0.7632.45

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: Low

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

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check Chrome version in browser

Navigate to chrome://version in the Chrome address bar and note the version number displayed next to 'Google Chrome'

Affected if The displayed version number is less than 145.0.7632.45 (for example, 145.0.7632.44 or earlier)
Check Chrome version via command line

Open a terminal and run 'google-chrome --version' or 'chromium --version' depending on the installation

Affected if The reported version is less than 145.0.7632.45
Verify Chrome version in About dialog

Click the three-dot menu, select 'Help', then 'About Google Chrome' and observe the version displayed

Affected if The version shown is prior to 145.0.7632.45
Confirm file input component is accessible

Open any web page with an HTML file input element (<input type='file'>) and verify it renders

Affected if The file input component loads and the Chrome version is below 145.0.7632.45 (the vulnerable component is present)

The user is affected if their installed Google Chrome version is less than 145.0.7632.45, as the UI spoofing flaw in the File input component exists in those versions.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 145.0.7632.45 or later

Fixed in 145.0.7632.45

Interim mitigation

Update Google Chrome to version 145.0.7632.45 or later. Organizations should deploy browser updates through their patch management systems to ensure all users receive the fix.

Recommended fix High confidence

Chrome version 145.0.7632.45 or later

Check the current Chrome version by navigating to chrome://settings/help
For automatic updates: Chrome should automatically update; wait for the update to complete and restart the browser
For manual update: Visit the Chrome download page (google.com/chrome) and download the latest version
Alternatively, use system package manager to update (e.g., apt update && apt upgrade on Debian/Ubuntu, or yum update on RHEL/Fedora)
After updating, verify the version by navigating to chrome://settings/help to confirm version 145.0.7632.45 or later is installed
Restart Chrome to ensure the security patch is fully applied

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory

Consultation1.0 h
Implementation2.0 h
Testing1.0 h
Review / QA1.0 h

5.0 hours of engineering $890

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-2322 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

chromereleases.googleblog.comRelease NotesVendor Advisory
issues.chromium.orgPermissions Required
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2322 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-2322?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsUpgrade to 145.0.7632.45 or later

Severity 5.4 Medium

Exploit likelihood EPSS, next 30 days 0.2%

Affects: Chrome

Remediation

Need this fixed?

Fix this in Chrome 5 hrs · Low

Typical engagement from $890

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2026-2322 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References