CVE-2025-33195
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 unexpected memory buffer operations. A successful exploit of this vulnerability might lead to data tampering, denial of service, or escalation of privileges.
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 where an attacker could cause unexpected memory buffer operations. Successful exploitation may lead to data tampering, denial of service, or privilege escalation.
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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 if system is a DGX Spark GB10Check the system model or product name via `dmidecode -s system-product-name` or check physical labels on the chassisAffected if The system model does not contain 'DGX Spark' or 'GB10' - not affected if it's a different NVIDIA DGX model or non-DGX system
-
Verify DGX OS is installedCheck for NVIDIA DGX OS by reviewing `/etc/os-release` or running `cat /etc/dgx-release` if availableAffected if No DGX OS is present - not in scope for this vulnerability
-
Check SROOT firmware versionUse NVIDIA system management tools (such as `nvsm` or vendor-specific firmware querying utilities) to retrieve the SROOT firmware version. Consult NVIDIA documentation for the exact command for your DGX OS version.Affected if The SROOT firmware version cannot be determined or is running without a patch - all versions of DGX OS are affected per the advisory; compare against any NVIDIA-provided fixed version when released
-
Verify SROOT firmware is loaded or activeCheck system firmware status via BMC/IPMI interfaces or NVIDIA management tooling to see if SROOT firmware component is currently active on the systemAffected if SROOT firmware is present and active on the system - vulnerability is applicable
-
Review system logs for memory anomaliesExamine system event logs, BMC logs, or kernel logs for unexpected memory buffer operations, crashes, or privilege escalation indicators that may correlate with exploitation attemptsAffected if Unusual memory-related events or buffer operation errors are present in logs without known cause
If the system is a NVIDIA DGX Spark GB10 running DGX OS with active SROOT firmware, it is affected since all versions are in the affected product range per the CVE.
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 NVIDIA-provided firmware update for SROOT when available; prioritize rapid deployment given the high CVSS score and potential for privilege escalation.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-33195 — 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-33195 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