dbcve.org
ChromeWeb browser · Google

CVE-2026-14117

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-30
Fix available
A fix is available. Upgrade to 150.0.7871.47 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable No privileges 7 weeks old

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
Insufficient validation of untrusted input in DevTools in Google Chrome on Windows prior to 150.0.7871.47 allowed a remote attacker who convinced a user to engage in specific UI gestures to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Low)

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 · high confidence

Insufficient validation of untrusted input in Chrome DevTools on Windows prior to version 150.0.7871.47 allows a remote attacker who tricks a user into performing specific UI gestures to potentially extract sensitive information from process memory via a crafted HTML page.

MitigationUpgrade Google Chrome to version 150.0.7871.47 or later on all Windows systems. Users should avoid engaging with untrusted UI gestures from unknown sources.

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

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

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

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. Verify Google Chrome is installed on Windows
    Check for Google Chrome installation by looking for chrome.exe in common locations: C:\Program Files\Google\Chrome\Application\chrome.exe or C:\Program Files (x86)\Google\Chrome\Application\chrome.exe. Use PowerShell command: Test-Path 'C:\Program Files\Google\Chrome\Application\chrome.exe'
    Affected if Chrome is not installed on the system
  2. Determine installed Google Chrome version
    Launch Chrome, navigate to chrome://settings/help, or use PowerShell: (Get-Item 'C:\Program Files\Google\Chrome\Application\chrome.exe').VersionInfo.ProductVersion
    Affected if Cannot determine the installed version
  3. Compare installed version against affected range
    Compare the detected version number to 150.0.7871.47. Any version less than 150.0.7871.47 is affected (e.g., 150.0.7871.40, 149.0.2623.112, etc.)
    Affected if Installed version is less than 150.0.7871.47
  4. Confirm Windows operating system
    Verify the system is running Windows. Run 'systeminfo | findstr /B /C:"OS Name"' or check system properties. This vulnerability only affects Chrome on Windows, not macOS or Linux
    Affected if System is not running Windows (vulnerability does not apply to other operating systems)

User is affected if Google Chrome is installed on Windows with a version lower than 150.0.7871.47

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 150.0.7871.47 or later
Fixed in 150.0.7871.47
Interim mitigation

Upgrade Google Chrome to version 150.0.7871.47 or later on all Windows systems. Users should avoid engaging with untrusted UI gestures from unknown sources.

Recommended fix High confidence

Chrome 150.0.7871.47 or later

  1. Open Google Chrome and navigate to Settings > Help > About Google Chrome
  2. Verify the current version is 150.0.7871.47 or later. If an earlier version is shown, Chrome will automatically check for updates and prompt you to restart to complete the update.
  3. Alternatively, download the latest Chrome version from the official Google Chrome website to ensure you have version 150.0.7871.47 or newer.

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14117 — 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-14117 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