PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-24218 NVIDIA CVE debrief

CVE-2026-24218 describes a provisioning flaw in NVIDIA DGX OS where cloning a base image causes identical SSH host keys to be deployed across multiple systems. Reusing the same host identity across hosts weakens SSH trust and can let an attacker impersonate a machine or position as a man-in-the-middle during administration and automation. The published CVSS 3.1 vector indicates network reachability with high attack complexity but no privileges or user interaction, and the stated impact spans confidentiality, integrity, and availability.

Vendor
NVIDIA
Product
DGX Spark
CVSS
HIGH 8.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-05-20
Original CVE updated
2026-05-21
Advisory published
2026-05-20
Advisory updated
2026-05-21

Who should care

NVIDIA DGX OS operators, infrastructure and provisioning teams, cluster administrators, and security teams that rely on SSH trust for fleet management, automation, or remote administration.

Technical summary

The supplied NVD and NVIDIA PSIRT-linked references describe a factory provisioning issue in which a cloned base image results in duplicate SSH host keys across DGX OS systems. Because SSH host keys are meant to uniquely identify a server, duplicated keys undermine host authenticity and can enable impersonation or man-in-the-middle attacks against management traffic. The record maps the issue to CWE-321 and assigns CVSS 3.1 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).

Defensive priority

High. Fleet-wide SSH identity reuse can affect trust boundaries for administrative access, automation, and monitoring, so affected provisioning workflows should be reviewed and remediated promptly.

Recommended defensive actions

  • Identify DGX OS systems provisioned from the affected cloned base image or factory workflow.
  • Verify that every host has a unique SSH host key set; regenerate keys on any systems that share identifiers.
  • Follow NVIDIA's advisory guidance for CVE-2026-24218 and apply any available update or provisioning fix.
  • Remove stale SSH trust records such as known_hosts entries, automation inventories, and bastion allowlists, then re-establish trust after key replacement.
  • If shared keys may have been exposed, rotate credentials and review SSH-authenticated administrative activity for signs of interception or tampering.
  • Update imaging and provisioning pipelines so per-host cryptographic identifiers are generated uniquely instead of being copied from a base image.

Evidence notes

This debrief is based on the supplied NVD CVE record, the CVE.org entry, and the NVIDIA PSIRT-linked advisory reference included in the source corpus. The corpus explicitly states that factory provisioning clones a base image and deploys identical SSH host keys across multiple systems. Vendor attribution was treated cautiously because the provided metadata marked it low-confidence, but the technical description and linked reference point to NVIDIA DGX OS. No exploit instructions or unsupported remediation details are included.

Official resources

Publicly disclosed on 2026-05-20 via the CVE record and the NVIDIA PSIRT-linked advisory reference in the supplied corpus. No KEV entry was supplied.