Answer in brief
CVE-2025-71422 records a Medium severity (CVSS 6.9) vulnerability in Contrast before 1.12.1 Insecure LUKS2 Persistent Storage. The current sources do not mark it as known exploited. The current feed maps edgelesssys/contrast (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps edgelesssys/contrast (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| edgelesssys/contrastgeneric | >=0 <1.12.1 | 1.12.1 |
Published upstream
Sep 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 27, 2026
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.
Quoted source text, attributed separately from HOL analysis.