Local disclosure or service interruption via precanonicalization validation
Published Nov 25, 2025 · Updated Nov 25, 2025
Incorrect input processing in NVIDIA DGX Spark before OTA0 allows local users to disclose information or interrupt service. The SROOT firmware validates attacker-controlled input before canonicalizing it, allowing a post-validation representation to evade the original check. Exploitation requires local access but no privileges or user interaction; NVIDIA does not identify the exposed data or whether interruption means a hang, crash, or reboot.
Summary
What happened
Incorrect input processing in NVIDIA DGX Spark before OTA0 allows local users to disclose information or interrupt service. The SROOT firmware validates attacker-controlled input before canonicalizing it, allowing a post-validation representation to evade the original check. Exploitation requires local access but no privileges or user interaction; NVIDIA does not identify the exposed data or whether interruption means a hang, crash, or reboot.
The record
- CVE
- CVE-2025-33194
- Published
- Nov 25, 2025
- Updated
- Nov 25, 2025
- Vendor
- DPDK Project
- Product
- DGX Spark
- Classifications
- CWE-180
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 25, 2025CVE publishedPublication date reported by the CVE source.
- Nov 25, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=All versions prior to OTA0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo