dbcve.org
ChromeWeb browser · Google

CVE-2026-2319

HIGH · 7.5 CVSS v3.1 Published 2026-02-11
Fix available
A fix is available. Upgrade to 145.0.7632.45 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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.

NVD · unedited
Race in DevTools in Google Chrome prior to 145.0.7632.45 allowed a remote attacker who convinced a user to engage in specific UI gestures and install a malicious extension to potentially exploit object corruption via a malicious file. (Chromium security severity: Medium)

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.

dbcve analysis · moderate confidence

A race condition vulnerability exists in Google Chrome DevTools prior to version 145.0.7632.45. A remote attacker can exploit this by convincing a user to perform specific UI gestures and install a malicious extension, leading to potential object corruption when processing a malicious file.

MitigationUpdate Chrome to version 145.0.7632.45 or later; avoid installing untrusted extensions and refrain from following untrusted prompts for specific UI gestures.

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

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.

NVD · CPE data
ChromeWeb browser
Affected:< 145.0.7632.45

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.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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.

dbcve checks

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

  1. Check installed Chrome version
    Navigate to chrome://settings/help or use the Chrome menu > Help > About Google Chrome to view the current version number
    Affected if The displayed version is lower than 145.0.7632.45
  2. Check for untrusted or unknown extensions
    Navigate to chrome://extensions/ and review the list of installed extensions. Look for any extensions that were not intentionally installed or that come from untrusted sources
    Affected if Any unknown, untrusted, or recently installed malicious extension is present in the browser
  3. Check DevTools usage patterns
    Monitor for processes related to DevTools (chrome-devtools:// or devtools remote debugging ports). Check browser logs or process activity for DevTools initialization
    Affected if DevTools has been actively used in the browser session
  4. Check for suspicious file handling
    Review recent file downloads and any files that may have been opened through DevTools or the browser. Check browser download history for unexpected files
    Affected if A user has recently opened or processed a file from an untrusted source through the browser

You are affected if your Chrome version is below 145.0.7632.45 AND you have installed a malicious extension AND performed specific UI gestures while processing a malicious file in DevTools

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 145.0.7632.45 or later
Fixed in 145.0.7632.45
Interim mitigation

Update Chrome to version 145.0.7632.45 or later; avoid installing untrusted extensions and refrain from following untrusted prompts for specific UI gestures.

Recommended fix High confidence

145.0.7632.45

  1. Open Google Chrome browser
  2. Navigate to Chrome menu (three dots) > Help > About Google Chrome (or go to chrome://settings/help)
  3. Chrome will automatically check for updates
  4. If version below 145.0.7632.45 is shown, click 'Update Google Chrome' to download and install the fix
  5. Restart the browser to apply the update
  6. Verify the update by returning to About Google Chrome and confirming version 145.0.7632.45 or later is installed

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2319 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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