dbcve.org
Geforce ExperienceApplication · Nvidia

CVE-2021-23175

HIGH · 8.2 CVSS v3.1 Published 2021-12-23
Fix available
A fix is available. Upgrade to 3.24.0.126 or later.
See remediation →
82/100
Remediation priority · High

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 a vulnerability in user authorization, where GameStream does not correctly apply individual user access controls for users on the same device, which, with user intervention, may lead to escalation of privileges, information disclosure, data tampering, and denial of service, affecting other resources beyond the intended security authority of GameStream.

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 contains an authorization bypass vulnerability in GameStream where per-user access controls are not correctly enforced for multiple users on the same device. This allows a user to access resources or perform actions beyond their intended security boundaries, potentially affecting other users on the system.

MitigationApply the NVIDIA GeForce Experience security update when available to correct the GameStream authorization logic and ensure proper per-user access controls are enforced.

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.24.0.126

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/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 if NVIDIA GeForce Experience is installed
    Open Windows Settings > Apps & Features (or use PowerShell: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*NVIDIA GeForce Experience*'})
    Affected if The application is not installed or not found, the vulnerability does not apply.
  2. Identify installed GeForce Experience version
    Open Control Panel > Programs and Features, find NVIDIA GeForce Experience and note the version in the Version column. Alternatively, right-click the GeForce Experience desktop shortcut, select Properties, and check the Details tab.
    Affected if Version is present and is lower than 3.24.0.126 (for example, 3.23.0.95, 3.22.0.112, etc.)
  3. Verify if GameStream is enabled
    Open GeForce Experience, go to Settings (gear icon), then to SHIELD. Check if GameStream is toggled ON or if 'Connect' is available. Also check: reg query 'HKLM:\SOFTWARE\NVIDIA Corporation\NvContainer\GameStream' /v Enabled
    Affected if GameStream is enabled or has been configured (the vulnerability only applies when GameStream functionality is active).
  4. Confirm multiple user accounts exist on the system
    Open Computer Management > Local Users and Groups > Users, or run 'net user' in Command Prompt to list all accounts.
    Affected if More than one user account exists on the machine (the vulnerability specifically allows one user to access resources intended for another user on the same device).

If GeForce Experience version is below 3.24.0.126 AND GameStream is enabled on a system with multiple user accounts, the environment is affected by this vulnerability.

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.24.0.126 or later
Fixed in 3.24.0.126
Interim mitigation

Apply the NVIDIA GeForce Experience security update when available to correct the GameStream authorization logic and ensure proper per-user access controls are enforced.

Recommended fix High confidence

Geforce Experience 3.24.0.126 or later

  1. Check the current version of NVIDIA GeForce Experience installed on the system
  2. Navigate to the official NVIDIA GeForce Experience download page at nvidia.custhelp.com or nvidia.com
  3. Download the latest version of GeForce Experience (version 3.24.0.126 or higher)
  4. Close any running instances of GeForce Experience
  5. Run the installer and follow the on-screen prompts to update the software
  6. Restart the computer if prompted to ensure the update completes successfully
  7. Verify the installed version is 3.24.0.126 or later

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

Fix this in Geforce Experience Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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