VulnerabilityPublished 25 Nov 2025

CVE-2025-33196: NVIDIA DGX Spark · Sensitive Information in Resource Not Removed Before Reuse

Affects NVIDIA DGX SparkSource CVE Database V5

Not known to be exploited · CVSS 4.4 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

4.4Medium

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

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

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
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: 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: 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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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 25 Nov 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 or the CVSS exploit maturity 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

Immediately restrict and monitor privileged local access to NVIDIA DGX Spark systems to trusted personnel only, employing strict access controls and logging.
Implement network segmentation and isolation for DGX Spark nodes to reduce the risk of unauthorized local access.
Monitor system logs and firmware behavior for unusual activity that could indicate attempts to exploit this vulnerability.
Prepare to deploy the OTA0 firmware update from NVIDIA as soon as it is released, ensuring a tested and controlled update process.
Conduct regular audits of user privileges and remove unnecessary elevated permissions on DGX Spark systems.
Employ hardware-level security features such as secure boot and firmware integrity verification where supported.
Educate system administrators and security teams about the vulnerability and the importance of safeguarding privileged access.
Consider encrypting sensitive data in memory or using secure enclaves if supported by the platform to reduce exposure of residual data.

Description

NVIDIA DGX Spark GB10 contains a vulnerability in SROOT firmware, where an attacker could cause a resource to be reused. A successful exploit of this vulnerability might lead to information disclosure.

Impact

For European organizations, particularly those involved in AI research, scientific computing, or data-intensive workloads using NVIDIA DGX Spark systems, this vulnerability poses a risk of sensitive data leakage. Confidentiality breaches could expose proprietary AI models, research data, or customer information, potentially leading to competitive disadvantage or regulatory non-compliance under GDPR. Since exploitation requires high privilege and local access, the threat is more relevant to insider threats or attackers who have already compromised internal systems. The lack of impact on integrity and availability limits the risk of operational disruption but does not reduce the importance of protecting sensitive information. Organizations in sectors such as finance, healthcare, and research institutions that deploy DGX Spark hardware in Europe should be vigilant. The medium severity rating suggests a moderate but non-critical risk, emphasizing the need for access controls and timely patching once updates become available.

CWE-226Sensitive Information in Resource Not Removed Before Reuse (opens in a new tab)
Base weakness
The product releases a resource such as memory or a file so that it can be made available for reuse, but it does not clear or "zeroize" the information contained in the resource before the product performs a critical state transition or makes the resource available for reuse by other entities.
Architecture and Design · Implementation
During critical state transitions, information not needed in the next state should be removed or overwritten with fixed patterns (such as all 0's) or random data, before the transition to the next state.
Architecture and Design · Implementation
When releasing, de-allocating, or deleting a resource, overwrite its data and relevant metadata with fixed patterns or random data. Be cautious about complex resource types whose underlying representation might be non-contiguous or change at a low level, such as how a file might be split into different chunks on a…
OWASP ASVS 4.0.3
V8.3.6 (opens in a new tab)
V8.3.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

Description

AI analysisMachine-generated, updated 2 Dec 2025, 18:52 UTC

WeaknessesCWE-226

Technical details

References

Community reviews

Related threats