Resource Reuse Information Disclosure in NVIDIA DGX Spark SROOT Firmware

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2025-33200?

CVE-2025-33200 is a vulnerability classified as Sensitive Information in Resource Not Removed Before Reuse, affecting DGX Spark (affected versions: All versions prior to OTA0). This vulnerability is rated Low, with a CVSS score of 3.3. Current sources do not report this vulnerability as exploited.

Overview

Original source data

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.

Affected products and scope

  • NVIDIA DGX Spark on NVIDIA DGX OS: affected in All versions prior to OTA0.
  • NVIDIA lists OTA0 as the updated version that addresses the issue.
  • The record's default status is unaffected; no other product branch or parallel release branch is confirmed by the available evidence.

Technical details

The flaw is in the SROOT firmware of NVIDIA DGX Spark and is classified as CWE-226, where sensitive information is not removed before a resource is reused. An attacker needs local access; both available assessments describe low attack complexity and no user interaction. NVIDIA's assessment describes a high-privilege requirement, while NVD's assessment describes a low-privilege requirement, so the exact privilege threshold remains unresolved. The record does not identify the resource type, code path, attacker-controlled input, or the specific condition that causes reuse.

Exploitability

  • Exploitation is local rather than network-reachable, and it does not require user interaction.
  • The available assessments describe low complexity, but they disagree on the required privilege level: NVIDIA records high privileges, while NVD records low privileges.
  • The supplied record marks public_exploit as false, but it does not establish whether the vulnerability has been exploited in the wild.
  • No named campaign, victim, specific exploit, or intrusion evidence is identified.

Technical impact

The flaw may cause sensitive data left in a resource to become available to a subsequent use of that resource, resulting in information disclosure. The available assessments describe a confidentiality impact but do not describe data modification or service disruption, and the affected scope remains within the vulnerable component. Organizational consequences could include local data exposure and investigation of workloads or accounts with access to the device. The record does not confirm code execution, privilege escalation, remote access, or a specific data-breach event.

Business impact

  • Sensitive information left in a resource may be disclosed when that resource is reused.
  • The documented risk is primarily to confidentiality; the available assessments do not describe an integrity or availability impact.
  • Because local access is required, prioritize devices with multiple local accounts, multi-user workloads, or processing of sensitive data.
  • The record does not identify the data type, exposure scope, or an actual data-leak incident, so it should not be treated as confirmation of a breach.

Remediation

  1. Update NVIDIA DGX OS on NVIDIA DGX Spark to OTA0, which NVIDIA lists as including the security update.
  2. Use NVIDIA's DGX OS update guidance and verify the resulting version on every device.
  3. If the update cannot yet be applied, isolate affected devices from unnecessary users or workloads and reduce local access within operational constraints. This is risk reduction, not a vendor-confirmed fix.
  4. Assess any release branch or variant not described by the advisory separately; do not assume it is protected merely because OTA0 is the update listed for the documented branch.

Detection

  1. Inventory NVIDIA DGX Spark GB10 devices and identify the NVIDIA DGX OS deployment on each system.
  2. Check the installed DGX OS and SROOT firmware versions, then compare them with the update NVIDIA identifies as addressing the issue.
  3. Confirm that the update completed and that the device booted with the updated firmware, rather than only confirming that an update package was downloaded.
  4. Review local telemetry for anomalous access to data handled by SROOT. Treat this as a precautionary check because the advisory does not provide a specific IOC or log event; the absence of suspicious logs does not prove that a system is safe.
Sources (18)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.