CVE-2025-23288VulnerabilityPublished 2 Aug 2025Updated 4 Aug 2025

CVE-2025-23288: NVIDIA GPU Display Drivers · CWE-497

Affects NVIDIA GPU Display DriversSource CVE Database V5

Not known to be exploited · CVSS 3.3 Low.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

3.3Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate this vulnerability effectively, European organizations should: 1) Monitor and inventory all systems running NVIDIA GPU Display Drivers, focusing on versions R535, R570, and R575. 2) Apply vendor patches promptly once they become available; in the absence of patches, consider rolling back to earlier, unaffected driver versions if feasible. 3) Restrict local access to systems with affected drivers by enforcing strict access controls, including limiting user privileges and implementing robust endpoint security solutions. 4) Employ application whitelisting and behavior monitoring to detect unusual local activity that could indicate exploitation attempts. 5) Conduct regular security awareness training to reduce the risk of initial compromise that could lead to local access. 6) Use network segmentation to isolate critical systems with GPU drivers, minimizing the risk of lateral movement. 7) Maintain up-to-date threat intelligence to identify any emerging exploits targeting this vulnerability.

Description

NVIDIA GPU Display Driver for Windows contains a vulnerability where an attacker may cause an exposure of sensitive system information with local unprivileged system access. A successful exploit of this vulnerability may lead to Information disclosure.

Impact

For European organizations, the primary impact of CVE-2025-23288 is the potential leakage of sensitive system information on machines running the affected NVIDIA GPU drivers. This could include details that facilitate further exploitation or reconnaissance by attackers. While the vulnerability itself does not directly compromise system integrity or availability, the disclosed information could be used to craft more targeted attacks, especially in environments where NVIDIA GPUs are deployed in workstations, servers, or high-performance computing clusters. Organizations in sectors such as finance, research, and manufacturing that rely on GPU-accelerated computing might be at higher risk. The requirement for local unprivileged access limits the threat to scenarios where an attacker has already gained some foothold, such as through phishing or insider threats. However, the widespread use of NVIDIA GPUs in European enterprises and institutions means that the vulnerability could be a vector for lateral movement or privilege escalation if combined with other vulnerabilities or attack techniques.

CWE-497Exposure of Sensitive System Information to an Unauthorized Control Sphere (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.
Architecture and Design · Implementation
Production applications should never use methods that generate internal details such as stack traces and error messages unless that information is directly committed to a log that is not viewable by the end user.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V14.3.2 (opens in a new tab)
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
Attack patterns
Web Application Fingerprinting (opens in a new tab)
System Location Discovery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

nvidia.custhelp.com/app/answers/detail/a_id/5670 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 10 Aug 2025, 01:02 UTC

WeaknessesCWE-497

Technical details

References

Community reviews

Related threats