# CVE-2025-71422: Contrast before 1.12.1 Insecure LUKS2 Persistent Storage

> A malicious host can bypass LUKS2 encryption in Contrast secure persistent volumes, allowing plaintext access to confidential data.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Sep 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-3g67-j5vf-vm4v, GHSA-f5p4-p5q5-jv3h, GO-2025-4078

## What is CVE-2025-71422?

CVE-2025-71422 is a medium-severity vulnerability in edgelesssys contrast, published on 27 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Contrast is a Kubernetes runtime for confidential containers. In versions before 1.12.1, the secure persistent volume feature is vulnerable to a malicious host supplying a crafted LUKS2 volume to a pod VM. LUKS2 volume metadata is not authenticated and, with cryptsetup versions prior to 2.8.1, a header specifying the null keyslot encryption algorithm (cipher_null-ecb) is accepted without error. Because the Contrast Initializer assumes a device is protected if `cryptsetup open` succeeds with the secret seed, the guest will open the attacker-supplied volume and write secret data in plaintext, or under a volume key known to the attacker, allowing the host to read confidential data that should have been encrypted. Contrast v1.12.1 ships cryptsetup 2.8.1, which disables null ciphers in keyslots when the passphrase is non-empty; v1.13.0 adds detached-header validation in guest memory and integrity protection for secure persistent storage. Contrast persistent volumes were not integrity protected, so integrity impact is not considered.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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

3 open source packages ship an affected version, including github.com/edgelesssys/contrast.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/edgelesssys/contrast` | Go | All versions | 1.12.1 |
| `github.com/edgelesssys/contrast` | Go | All versions | 1.12.1 |
| `github.com/edgelesssys/contrast` | Go | All versions | 1.12.1 |

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

Upgrade github.com/edgelesssys/contrast to 1.12.1 or later.

## Is CVE-2025-71422 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-71422 is a medium-severity vulnerability in edgelesssys contrast, published on 27 Sep 2026. 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-71422 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/edgelesssys/contrast (Go): affected all versions; fixed in 1.12.1
- github.com/edgelesssys/contrast (Go): affected all versions; fixed in 1.12.1
- github.com/edgelesssys/contrast (Go): affected all versions; fixed in 1.12.1

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-71422/ (Markdown: https://insights.sbomify.com/CVE-2025-71422/index.md)
```

## Sources

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

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