Out-of-Bounds Read in NVIDIA DGX Spark (CVE-2026-24225)
Summary
Vulnerability in NVIDIA DGX Spark (CVE-2026-24225). Confidential information can be exposed externally.
Original description
The description as published by the source.
NVIDIA DGX Spark contains a vulnerability in the standalone MM firmware where an attacker could be able to cause an out-of-bounds read. A successful exploit of this vulnerability might lead to information disclosure.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-24225 has been found in NVIDIA DGX Spark.
Confidential information can be exposed externally. CVSS score: 6.0/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "NVIDIA DGX Spark CVE-2026-24225" on the vendor's site.
CVE-2026-24225 (NVIDIA DGX Spark) — CWE-125 / CVSS v3 6.0
Attack vector: local / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Out-of-bounds read (CWE-125) exists in NVIDIA DGX Spark.
Check the vendor advisory for the affected versions of NVIDIA DGX Spark.
Severity: Medium (CVSS 6.0/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで NVIDIA DGX Spark を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory psirt@nvidia.com
- web psirt@nvidia.com
- web psirt@nvidia.com
- web github.com