{"id":"CVE-2025-71422","title":"Contrast is a Kubernetes runtime for confidential containers","summary":"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 au…","severity":"medium","cvss":5.7,"cvssVector":"CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","cwe":["CWE-347"],"vendor":"edgelesssys","product":"contrast","affected":["contrast < 1.12.1"],"published":"2026-09-27","updated":"2026-09-27","sourceUpdated":"2026-09-27T02:17:11.040","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2025-71422","references":[{"url":"https://github.com/edgelesssys/contrast/security/advisories/GHSA-f5p4-p5q5-jv3h","label":"disclosure@vulncheck.com"},{"url":"https://www.vulncheck.com/advisories/contrast-before-1.12.1-insecure-luks2-persistent-storage","label":"disclosure@vulncheck.com"}],"tags":["nvd","cve.org"],"ingestedAt":"2026-09-27T02:41:45.560Z","slug":"CVE-2025-71422","body":"## Overview\n\nContrast 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.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":31,"depthScoreParts":{"impact":31.4,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}