dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2025-23347

HIGH · 7.8 CVSS v3.1 Published 2025-10-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 Project G-Assist contains a vulnerability where an attacker might be able to escalate permissions. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, data tampering, denial of service, and information disclosure.

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

NVIDIA Project G-Assist contains a privilege escalation vulnerability that allows an attacker to gain elevated permissions. Successful exploitation could result in arbitrary code execution, privilege escalation, data tampering, denial of service, and information disclosure.

MitigationApply the NVIDIA security patch when available. Until then, restrict user permissions to the minimum required, limit network exposure of affected systems, and monitor for suspicious activity indicative of privilege escalation attempts.

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

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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. Verify NVIDIA Project G-Assist is installed
    Check for G-Assist installation by reviewing installed programs in Windows Settings > Apps & Features, or check the NVIDIA application directory (typically under C:\Program Files\NVIDIA Corporation or C:\Users\[user]\AppData\Local\NVIDIA), or use command: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like '*G-Assist*'}
    Affected if NVIDIA Project G-Assist is present on the system
  2. Identify the installed G-Assist version
    Right-click the G-Assist executable (if found), select Properties, and check the Details tab for version information; alternatively, run: (Get-Item 'C:\Program Files\NVIDIA Corporation\*\G-Assist.exe' -ErrorAction SilentlyContinue).VersionInfo.FileVersion or check within the application About section
    Affected if Version cannot be determined or is lower than the fixed version NVIDIA publishes for this CVE
  3. Confirm G-Assist service or process is active
    Open Task Manager or run: Get-Process | Where-Object {$_.ProcessName -like '*G-Assist*'}; also check services.msc for any NVIDIA G-Assist related service
    Affected if G-Assist executable or service is currently running with elevated privileges
  4. Review user account modifications
    Check Windows Event Viewer under Security logs for Event ID 4720 (user account created), 4726 (user account deleted), or 4732 (member added to security-enabled local group); also run: Get-LocalUser to enumerate all local accounts
    Affected if New unauthorized user accounts appear or unexpected accounts are added to Administrator groups
  5. Check for privilege escalation indicators
    Review audit logs for failed privilege escalation attempts; run: Get-WinEvent -FilterHashtable @{LogName='Security';ID=4672} -MaxEvents 50 to see accounts granted special privileges; look for any NVIDIA G-Assist processes spawning child processes with SYSTEM privileges
    Affected if G-Assist-related processes exhibit unexpected elevated behavior or spawn processes outside normal operation

The system is affected if NVIDIA Project G-Assist is installed and running, and the installed version matches the vulnerable versions NVIDIA has identified for CVE-2025-23347.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the NVIDIA security patch when available. Until then, restrict user permissions to the minimum required, limit network exposure of affected systems, and monitor for suspicious activity indicative of privilege escalation attempts.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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