CVE-2025-33200VulnerabilityPublished 25 Nov 2025

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

Affects NVIDIA DGX SparkSource CVE Database V5

Not known to be exploited · CVSS 2.3 Low.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

2.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:H/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: High
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: 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: 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 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 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

1. Monitor NVIDIA’s official channels for the release of the OTA0 firmware update and apply it promptly to all DGX Spark GB10 systems. 2. Restrict and tightly control administrative and high-privilege access to DGX Spark systems to minimize the risk of local exploitation. 3. Implement strict access controls and auditing on systems hosting DGX Spark to detect and prevent unauthorized privilege escalation. 4. Use hardware and software-based security features such as secure boot and firmware integrity verification to prevent unauthorized firmware modifications. 5. Segregate DGX Spark systems within secure network zones to limit exposure to potential attackers. 6. Conduct regular security training for administrators to recognize and prevent insider threats. 7. If firmware updates are delayed, consider additional data encryption at rest and in use to reduce the impact of potential data leakage. 8. Review and enhance logging and monitoring to detect suspicious activities related to resource reuse or memory access on these systems.

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, the primary impact of CVE-2025-33200 is the potential disclosure of sensitive information processed on NVIDIA DGX Spark systems. These platforms are often used in AI research, scientific computing, and data analytics, where confidentiality of data is critical. Exposure of residual data could lead to leakage of proprietary algorithms, research data, or personal information, potentially violating data protection regulations such as GDPR. Although the vulnerability requires high privilege local access, insider threats or compromised administrative accounts could exploit it. The low CVSS score reflects limited impact on system functionality, but the confidentiality breach risk remains significant in sensitive environments. Organizations relying on DGX Spark for critical workloads may face reputational damage or competitive disadvantage if sensitive data is disclosed. The absence of known exploits reduces immediate risk, but the specialized nature of the hardware means that affected organizations are likely to be those with advanced AI or HPC infrastructure, which are strategically important in Europe’s digital and research sectors.

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:49 UTC

WeaknessesCWE-226

Technical details

References

Community reviews

Related threats