dbcve.org
Geforce ExperienceApplication · Nvidia

CVE-2022-31611

HIGH · 7.3 CVSS v3.1 Published 2023-02-07
Fix available
A fix is available. Upgrade to 3.27.0.112 or later.
See remediation →
73/100
Remediation priority · Elevated

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
NVIDIA GeForce Experience contains an uncontrolled search path vulnerability in all its client installers, where an attacker with user level privileges may cause the installer to load an arbitrary DLL when the installer is launched. A successful exploit of this vulnerability could lead to escalation of privileges and code execution.

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

NVIDIA GeForce Experience installer suffers from an uncontrolled search path vulnerability (DLL hijacking). The installer does not use fully qualified paths when loading DLLs, causing it to search configurable directories. An attacker with user-level access can place a malicious DLL in a directory the installer searches, achieving privilege escalation and code execution when the installer runs with elevated privileges.

MitigationUse official NVIDIA channels only, verify installer integrity via checksums, and run installers from clean directories without user-writable locations in the PATH. Apply vendor patches when available.

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
Geforce ExperienceApplication
Affected:< 3.27.0.112

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
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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. Locate GeForce Experience installation directory
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\GeForce Experience, or check C:\Program Files\NVIDIA Corporation\GeForce Experience for the installation folder
    Affected if The software is installed in any directory on the system
  2. Find installed version number
    Right-click the GeForceExperience.exe file in the installation directory, select Properties, and view the File version on the Details tab
    Affected if The displayed version is lower than 3.27.0.112
  3. Alternative: Check version via PowerShell
    Run Get-ItemProperty 'C:\Program Files\NVIDIA Corporation\GeForce Experience\GeForceExperience.exe' | Select-Object -ExpandProperty VersionInfo
    Affected if The version output shows a build number below 3.27.0.112
  4. Check if installer files exist on system
    Search for any NVIDIA GeForce Experience installer executables (e.g., Geforce_Experience.exe) in user-accessible directories like Downloads or Desktop
    Affected if An older installer version (<3.27.0.112) exists in a user-writable location and has not been deleted after installation

You are affected if GeForce Experience version 3.27.0.112 or higher is NOT installed on the system, indicating a vulnerable installer was or could be used.

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

Use official NVIDIA channels only, verify installer integrity via checksums, and run installers from clean directories without user-writable locations in the PATH. Apply vendor patches when available.

Recommended fix High confidence

GeForce Experience 3.27.0.112 or later

  1. Navigate to the official NVIDIA website and download the latest GeForce Experience installer
  2. Ensure you download from nvidia.com or a trusted NVIDIA source
  3. Run the downloaded installer with administrator privileges
  4. Follow the on-screen prompts to complete the installation
  5. Restart your computer if prompted to ensure all NVIDIA services load the updated version

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

Fix this in Geforce Experience Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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