# CVE-2026-24218: Hardcoded credentials in DGX Spark

> Identical SSH host keys in NVIDIA DGX OS allow host impersonation and man-in-the-middle attacks, leading to code execution and privilege escalation.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 May 2026
- **Updated:** 21 May 2026
- **Also known as:** GHSA-849r-hj58-p84g

## What is CVE-2026-24218?

CVE-2026-24218 is a high-severity vulnerability in NVIDIA DGX Spark, published on 20 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2026-24218?

It affects 1 product.


Products: Nvidia Dgx Os.

## How do I fix CVE-2026-24218?

No fix has been published for CVE-2026-24218 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-24218 being exploited?

There is no known exploitation of CVE-2026-24218 in the wild and no public exploit code.

## Other vulnerabilities in NVIDIA DGX Spark

- [CVE-2025-33187](https://insights.sbomify.com/CVE-2025-33187/): Privilege escalation in DGX Spark (critical 9.3)
- [CVE-2025-33188](https://insights.sbomify.com/CVE-2025-33188/): Privilege escalation in DGX Spark (high 8.0)
- [CVE-2025-33189](https://insights.sbomify.com/CVE-2025-33189/): Memory corruption in DGX Spark (high 7.8)
- [CVE-2025-33190](https://insights.sbomify.com/CVE-2025-33190/): Memory corruption in DGX Spark (medium 6.7)
- [CVE-2025-33191](https://insights.sbomify.com/CVE-2025-33191/): Denial of service in DGX Spark (medium 5.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24218 and fix it if it is affected.

What it is: CVE-2026-24218 is a high-severity vulnerability in NVIDIA DGX Spark, published on 20 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-24218 in the wild and no public exploit code.

Affected product: NVIDIA DGX Spark. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24218/ (Markdown: https://insights.sbomify.com/CVE-2026-24218/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24218
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24218
- OSV: https://osv.dev/vulnerability/CVE-2026-24218

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24218/
Summaries are generated and may contain mistakes; the official description above is the record.