DGX Spark: Use of Hard-coded Cryptographic Key
CVE-2026-24218 is a high-severity use of hard-coded cryptographic key vulnerability in DGX Spark from NVIDIA, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version OTA0 as the first without the flaw, so updating DGX Spark to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.6% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update DGX Spark to OTA0 or a later version.
- Read the advisory on nvidia.custhelp.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| NVIDIA | DGX Spark | before OTA0 | OTA0 |
| NVIDIA | Dgx OS | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (nvidia.com).
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Hard-coded Cryptographic Key
The product uses a hard-coded, unchangeable cryptographic key.
How developers prevent this class of flaw
- Prevention schemes mirror that of hard-coded password storage.
More Use of Hard-coded Cryptographic Key vulnerabilities (CWE-321)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- nvd.nist.gov/vuln/detail/CVE-2026-24218US Government Resource
- cve.org/CVERecord?id=CVE-2026-24218Third Party Advisory
Other vulnerabilities in DGX Spark
- 8.2 High severity
- 8.2 High severity
- 8.2 High severity
- 7.8 High severity
- 7.1 High severity
- 7.8 High severity
Recent Use of Hard-coded Cryptographic Key vulnerabilities
- 9.1 Critical severity
- 8.3 High severity
- 8.6 High severity
- 8.7 High severity
- 7.7 High severity
- 9.1 Critical severity
Spotted an error? Tell us.