CVE-2025-58356: edgelesssys constellation · Improper Verification of Cryptographic Signature
Affects edgelesssys constellationSource CVE Database V5
Not known to be exploited · CVSS 8.3 High : upgrade to 2.24.0 soon.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.24.0
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade edgelesssys/constellation to 2.24.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubedgelesssys/constellationpkg:github/edgelesssys/constellationOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Immediately upgrade cryptsetup to version 2.24.0 or later on all systems running edgelesssys Constellation to ensure proper handling of LUKS2 volumes and keyslot encryption algorithms.
- Audit existing encrypted volumes to detect any that use the cipher_null-ecb algorithm or other insecure keyslot configurations and re-encrypt them with secure algorithms.
- Implement strict cryptographic policy enforcement to reject LUKS2 volumes with null or insecure cipher algorithms during creation or mounting.
- Restrict local privileged access to trusted administrators and enforce strong access controls and monitoring to reduce the risk of exploitation.
- Regularly monitor and verify the integrity and encryption status of persistent storage volumes within Kubernetes clusters.
- Incorporate cryptographic validation checks into CI/CD pipelines and infrastructure as code to prevent deployment of vulnerable configurations.
- Stay informed on vendor patches and security advisories related to edgelesssys Constellation and cryptsetup components.
- Consider additional runtime security controls such as container security platforms that can detect anomalous volume mounts or access patterns.
Description
Constellation is the first Confidential Kubernetes. The Constellation CVM image uses LUKS2-encrypted volumes for persistent storage. When opening an encrypted storage device, the CVM uses the libcryptsetup function crypt_activate_by_passhrase. If the VM is successful in opening the partition with the disk encryption key, it treats the volume as confidential. However, due to the unsafe handling of null keyslot algorithms in the cryptsetup 2.8.1, it is possible that the opened volume is not encrypted at all. Cryptsetup prior to version 2.8.1 does not report an error when processing LUKS2-formatted disks that use the cipher_null-ecb algorithm in the keyslot encryption field. This vulnerability is fixed in 2.24.0.
References
- github.com/edgelesssys/constellation/security/advisories/GHSA-hq76-6gh2-5g4q (opens in a new tab)
- github.com/edgelesssys/constellation/pull/3927 (opens in a new tab)
- github.com/edgelesssys/constellation/releases/tag/v2.24.0 (opens in a new tab)
- blog.trailofbits.com/2025/10/30/vulnerabilities-in-luks2-disk-encryption-for-confidential-vms/ (opens in a new tab)