CVE-2025-33194
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedNVIDIA DGX Spark GB10 contains a vulnerability in SROOT firmware, where an attacker could cause improper processing of input data. A successful exploit of this vulnerability might lead to information disclosure or denial of service.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceNVIDIA DGX Spark GB10 contains a vulnerability in SROOT firmware (the root of trust component) where improper input processing could allow an attacker to cause information disclosure or denial of service. The vulnerability is in the firmware layer, specifically affecting how the SROOT component handles input data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the DGX system modelCheck the system model or product name to confirm it is a DGX Spark GB10. This may be visible in system inventory, BMC interface, or physical system labeling.Affected if The system is a DGX Spark GB10 and runs any version of DGX OS
-
Confirm DGX OS installationIdentify the installed DGX OS version using system inventory commands, BMC interfaces, or OS-level queries such as 'cat /etc/os-release' or equivalent system information utilities.Affected if DGX OS is installed (all versions are affected)
-
Locate SROOT firmware versionAccess the SROOT firmware version through the BMC/IPMI interface, NVIDIA system management tools, or firmware update utilities provided by NVIDIA. The SROOT component is the root of trust firmware.Affected if The SROOT firmware version matches the vulnerable version range or cannot be determined (all versions are affected per vendor advisory)
-
Check SROOT input processing configurationInspect SROOT configuration or firmware settings through NVIDIA-provided management interfaces to determine if the improper input processing vector is accessible or enabled.Affected if The SROOT component accepts external input and the vulnerable input handling code path is present
A user is affected if they operate a DGX Spark GB10 system running any version of DGX OS with a vulnerable SROOT firmware version.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply firmware updates from NVIDIA for the SROOT component on DGX Spark GB10 systems. Contact NVIDIA support to obtain the patched SROOT firmware version and follow their update procedures, which may involve secure boot re-provisioning.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-33194 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-33194 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data