File integrity bypass via ineffective LUKS validation
Published Aug 12, 2026 · Updated Aug 12, 2026
Integrity-check bypass in CPSD CryptoPro Secure Disk for BitLocker before 7.7.4 allows attackers to skip all CryptoPro file checks. The ss_gui pre-boot component treats the presence of LUKS encryption as sufficient validation and suppresses every CryptoPro file-integrity check. Reachability requires a LUKS-encrypted volume to be presented to the pre-boot environment; successful bypass leaves modified files unchecked and can compromise protected data confidentiality and integrity.
Summary
What happened
Integrity-check bypass in CPSD CryptoPro Secure Disk for BitLocker before 7.7.4 allows attackers to skip all CryptoPro file checks. The ss_gui pre-boot component treats the presence of LUKS encryption as sufficient validation and suppresses every CryptoPro file-integrity check. Reachability requires a LUKS-encrypted volume to be presented to the pre-boot environment; successful bypass leaves modified files unchecked and can compromise protected data confidentiality and integrity.
The record
- CVE
- CVE-2025-59324
- Published
- Aug 12, 2026
- Updated
- Aug 12, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-347, T1562.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 12, 2026CVE publishedPublication date reported by the CVE source.
- Aug 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo