CVE-2026-24218: CWE-321 Use of Hard-coded Cryptographic Key in NVIDIA DGX Spark
NVIDIA DGX OS has a vulnerability in its factory provisioning process where cloning a base image results in identical SSH host keys being deployed across multiple systems. This reuse of cryptographic identifiers allows potential host impersonation or man-in-the-middle attacks. Exploiting this vulnerability could lead to code execution, data tampering, privilege escalation, information disclosure, and denial of service. The vulnerability is tracked as CVE-2026-24218 with a high severity score of 8.1. No official patch or remediation guidance is currently available from the vendor. There are no known exploits in the wild at this time.
AI Analysis
Technical Summary
CVE-2026-24218 is a vulnerability in NVIDIA DGX OS related to the factory provisioning process. When a base image is cloned to provision multiple systems, identical SSH host keys are deployed across those systems. This hard-coded cryptographic key reuse (CWE-321) compromises the uniqueness of host identities, enabling attackers to impersonate hosts or perform man-in-the-middle attacks. The vulnerability impacts confidentiality, integrity, and availability, with a CVSS v3.1 score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). No patch or official remediation level has been published by NVIDIA as of the data provided.
Potential Impact
The vulnerability allows attackers to impersonate hosts or intercept communications due to shared SSH host keys across multiple DGX Spark systems. This can lead to severe impacts including unauthorized code execution, data tampering, escalation of privileges, information disclosure, and denial of service. The high CVSS score reflects the critical nature of these impacts. However, there are no known exploits in the wild currently.
Mitigation Recommendations
Patch status is not yet confirmed — check the NVIDIA vendor advisory for current remediation guidance. Until an official fix is released, organizations should avoid deploying cloned base images with identical SSH host keys or manually regenerate unique SSH host keys on each provisioned system to mitigate the risk of host impersonation and related attacks.
CVE-2026-24218: CWE-321 Use of Hard-coded Cryptographic Key in NVIDIA DGX Spark
Description
NVIDIA DGX OS has a vulnerability in its factory provisioning process where cloning a base image results in identical SSH host keys being deployed across multiple systems. This reuse of cryptographic identifiers allows potential host impersonation or man-in-the-middle attacks. Exploiting this vulnerability could lead to code execution, data tampering, privilege escalation, information disclosure, and denial of service. The vulnerability is tracked as CVE-2026-24218 with a high severity score of 8.1. No official patch or remediation guidance is currently available from the vendor. There are no known exploits in the wild at this time.
CVSS v3.1
Score 8.1high
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-24218 is a vulnerability in NVIDIA DGX OS related to the factory provisioning process. When a base image is cloned to provision multiple systems, identical SSH host keys are deployed across those systems. This hard-coded cryptographic key reuse (CWE-321) compromises the uniqueness of host identities, enabling attackers to impersonate hosts or perform man-in-the-middle attacks. The vulnerability impacts confidentiality, integrity, and availability, with a CVSS v3.1 score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). No patch or official remediation level has been published by NVIDIA as of the data provided.
Potential Impact
The vulnerability allows attackers to impersonate hosts or intercept communications due to shared SSH host keys across multiple DGX Spark systems. This can lead to severe impacts including unauthorized code execution, data tampering, escalation of privileges, information disclosure, and denial of service. The high CVSS score reflects the critical nature of these impacts. However, there are no known exploits in the wild currently.
Mitigation Recommendations
Patch status is not yet confirmed — check the NVIDIA vendor advisory for current remediation guidance. Until an official fix is released, organizations should avoid deploying cloned base images with identical SSH host keys or manually regenerate unique SSH host keys on each provisioned system to mitigate the risk of host impersonation and related attacks.
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: 05/20/2026, 19:34:39 UTC
Last enriched: 05/27/2026, 21:00:20 UTC
Last updated: 07/31/2026, 19:22:58 UTC
Views: 75
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.