Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-24218: CWE-321 Use of Hard-coded Cryptographic Key in NVIDIA DGX Spark

0
High
VulnerabilityCVE-2026-24218cvecve-2026-24218cwe-321
Published: Wed May 20 2026 (05/20/2026, 17:43:16 UTC)
Source: CVE Database V5
Vendor/Project: NVIDIA
Product: DGX Spark

Description

NVIDIA DGX OS contains a vulnerability in the factory provisioning process, where the cloning of a base image causes identical SSH host keys to be deployed across multiple systems. The sharing of cryptographic identifiers across all similarly provisioned systems enables host impersonation or attacker-in-the-middle attacks. A successful exploit of this vulnerability might lead to code execution, data tampering, escalation of privileges, information disclosure, and denial of service.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 05/20/2026, 19:49:20 UTC

Technical Analysis

CVE-2026-24218 is a vulnerability in NVIDIA DGX Spark's operating system factory provisioning process. When a base image is cloned to provision multiple systems, identical SSH host keys are duplicated across these systems. This hard-coded cryptographic key reuse (CWE-321) undermines the uniqueness of host identities, enabling host impersonation or man-in-the-middle attacks. The vulnerability has a CVSS v3.1 score of 8.1, indicating high impact on confidentiality, integrity, and availability. No vendor advisory or patch information is currently provided, and the affected versions are unspecified beyond '0'.

Potential Impact

The vulnerability allows attackers to impersonate legitimate hosts or intercept communications via man-in-the-middle attacks due to shared SSH host keys. Successful exploitation can result in code execution, data tampering, privilege escalation, information disclosure, and denial of service on affected NVIDIA DGX Spark systems. The high CVSS score reflects significant potential impact on system security and data confidentiality.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should avoid deploying cloned base images with identical SSH host keys or manually regenerate unique SSH host keys on each provisioned system to prevent host impersonation risks.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
nvidia
Date Reserved
2026-01-21T19:09:35.635Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 6a0e0ccfba1db473629e775b

Added to database: 5/20/2026, 7:34:39 PM

Last enriched: 5/20/2026, 7:49:20 PM

Last updated: 5/21/2026, 6:12:12 AM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses