# CVE-2025-59054: dstack has insecure LUKS2 persistent storage partitions that may be opened and used

> A malicious host can provide a crafted LUKS2 volume to dstack CVMs, leading to disclosure of secret keys and potential compromise of guest execution.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Sep 2025
- **Updated:** 28 Nov 2025
- **Also known as:** GHSA-jxq2-hpw3-m5wf

## What is CVE-2025-59054?

CVE-2025-59054 is a high-severity vulnerability in Dstack-TEE dstack, published on 12 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

dstack is a software development kit (SDK) to simplify the deployment of arbitrary containerized apps into trusted execution environments. In versions of dstack prior to 0.5.4, a malicious host may provide a crafted LUKS2 data volume to a dstack CVM for use as the `/data` mount. The guest will open the volume and write secret data using a volume key known to the attacker, causing disclosure of Wireguard keys and other secret information. The attacker can also pre-load data on the device, which could potentially compromise guest execution. LUKS2 volume metadata is not authenticated and supports null key-encryption algorithms, allowing an attacker to create a volume such that the volume opens (cryptsetup open) without error using any passphrase or token, records all writes in plaintext (or ciphertext with an attacker-known key), and/or contains arbitrary data chosen by the attacker. Version 0.5.4 of dstack contains a patch that addresses LUKS headers.

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

## Which versions are affected by CVE-2025-59054?


## How do I fix CVE-2025-59054?

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

## Is CVE-2025-59054 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59054 and fix it if it is affected.

What it is: CVE-2025-59054 is a high-severity vulnerability in Dstack-TEE dstack, published on 12 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59054 in the wild and no public exploit code.

Affected product: Dstack-TEE dstack. 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-2025-59054/ (Markdown: https://insights.sbomify.com/CVE-2025-59054/index.md)
```

## Sources

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

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