The secure persistent volume feature is susceptible to an attack where a malicious host provides a crafted LUKS2 volume to a pod VM. This occurs because LUKS2 volume metadata is not authenticated and `cryptsetup` versions prior to 2.8.1 accept a header specifying the null keyslot encryption algorithm (`cipher null-ecb`) without error. The Contrast Initializer assumes a device is protected if the `cryptsetup open` function succeeds with the secret seed. Consequently, the guest may open the attacker-supplied volume and write secret data in plaintext or using a volume key known to the attacker, enabling the host to read confidential data.