Skip to content
Hardware

CVE-2026-47626

8.2
High
EPSS 0.20%Aug 26, 2026

OOB write in NVIDIA DGX Spark firmware enabling code execution and privilege escalation.

common questions

Is CVE-2026-47626 being exploited?

Not confirmed. CVE-2026-47626 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.20% probability of exploitation in the next 30 days.

How severe is CVE-2026-47626?

CVE-2026-47626 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-47626?

Not known from our data. No patch reference has been recorded for CVE-2026-47626, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-47626 affect?

CVE-2026-47626 affects NVIDIA DGX Spark (system firmware). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-47626?

Isolate DGX systems, restrict admin access, audit logs, and apply vendor firmware updates when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
NVIDIA DGX Spark (system firmware)
impact

Out-of-bounds firmware write can lead to code execution, privilege escalation, denial of service, data tampering, and information disclosure.

action required

Immediate action required

affected versions
NVIDIA DGX Spark
  • affected0 to 1.110.12

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free