TPM unsealing via boot-state-insensitive PCR policy
Published Aug 12, 2026 · Updated Aug 12, 2026
Authentication bypass in CPSD CryptoPro Secure Disk for BitLocker before 7.7.4 allows attackers to unseal the TPM via an unintended boot path. The default TPM Platform Configuration Register policy omits system boot state from its sealing conditions, so the TPM evaluates an incomplete state when deciding whether to release sealed material. The gate is use of the default policy plus an unintended execution path or another hardware platform; the bounded consequence is release of TPM-sealed material.
Summary
What happened
Authentication bypass in CPSD CryptoPro Secure Disk for BitLocker before 7.7.4 allows attackers to unseal the TPM via an unintended boot path. The default TPM Platform Configuration Register policy omits system boot state from its sealing conditions, so the TPM evaluates an incomplete state when deciding whether to release sealed material. The gate is use of the default policy plus an unintended execution path or another hardware platform; the bounded consequence is release of TPM-sealed material.
The record
- CVE
- CVE-2025-59321
- Published
- Aug 12, 2026
- Updated
- Aug 12, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-1188
- 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