CVE-2025-23291VulnerabilityPublished 30 Sep 2025

CVE-2025-23291: DLS component of NVIDIA License System · Cleartext Storage of Sensitive Information

Affects DLS component of NVIDIA License SystemSource CVE Database V5

Not known to be exploited · CVSS 2.4 Low : upgrade to 3.5.1 when convenient.

Data as of 26 Oct 2026, 08:11 UTC

CVSS 3.1 base score

2.4Low

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

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

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

Attack Vector: Adjacent
Attack Complexity: High
Privileges Required: High
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: None
Availability: None

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

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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 30 Sep 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 26 Oct 2026.

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

Upgrade DLS component of NVIDIA License System to 3.5.1.

Affected software

Product	Affected	Fixed in
NVIDIA DLS component of NVIDIA License System	Affected <3.5.1 =3.1.7	Fixed in 3.5.1

AI-suggested

2) Restrict access to the DLS component and its storage locations to only essential personnel with strict role-based access controls, minimizing the number of users with high privileges. 3) Implement encryption at rest for all sensitive data managed by the licensing system, either through built-in features or external disk encryption solutions, to prevent cleartext exposure. 4) Monitor and audit access logs for unusual or unauthorized access attempts to the licensing system, enabling early detection of potential exploitation attempts. 5) Educate administrators and users with access about the risks of social engineering and phishing, as user interaction is required for exploitation. 6) Employ network segmentation to isolate the licensing system from broader enterprise networks, reducing the attack surface. 7) Regularly review and update security policies related to license management and sensitive data handling to incorporate lessons learned from this vulnerability. These steps go beyond generic advice by focusing on access control, encryption, monitoring, and user awareness tailored to the specifics of this vulnerability.

Description

NVIDIA Delegated Licensing Service for all appliance platforms contains a vulnerability where an User/Attacker may cause an authorized action. A successful exploit of this vulnerability may lead to information disclosure.

Impact

For European organizations, the impact of CVE-2025-23291 primarily revolves around the potential exposure of sensitive licensing information managed by NVIDIA's License System. While the direct impact on system integrity and availability is minimal, the confidentiality breach could lead to unauthorized use or duplication of licenses, resulting in financial losses and compliance issues. Organizations in sectors heavily reliant on NVIDIA hardware and software, such as research institutions, data centers, and enterprises utilizing GPU-accelerated computing, may face increased risk. Furthermore, exposure of licensing data could indirectly aid attackers in crafting more targeted attacks or bypassing software protections. Given the high privilege and user interaction requirements, the risk is somewhat mitigated but remains relevant in environments where trusted users or administrators might be compromised or act maliciously. The vulnerability also poses a risk to supply chain security if licensing information is leaked and exploited by third parties. Overall, while the immediate threat level is low, the potential for cascading effects on confidentiality and compliance in European organizations warrants attention.

CWE-312Cleartext Storage of Sensitive Information (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
Implementation · System Configuration · Operation
When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to encrypt the data at rest.
Implementation · System Configuration · Operation
In some systems/environments such as cloud, the use of "double encryption" (at both the software and hardware layer) might be required, and the developer might be solely responsible for both layers, instead of shared responsibility with the administrator of the broader system/environment.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (opens in a new tab)
Attack patterns
Retrieve Embedded Sensitive Data (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Sep 2025, 17:59 UTC

WeaknessesCWE-312

Technical details

References

Community reviews

Related threats