Security readout for executives and security teams
Plain-English summary
A weak default TPM policy can let protected disk keys be released without confirming the expected boot state. For systems using affected CPSD CryptoPro Secure Disk for BitLocker releases, this may undermine full-disk encryption and expose sensitive data through an unintended execution path or another hardware platform.
Executive priority
Treat this as an urgent encryption-control issue where affected CPSD versions protect valuable data. Accelerate inventory and remediation, but avoid characterizing it as an active attack campaign. Business impact depends on deployment scope and the practical prerequisites, which the supplied evidence does not fully establish.
Technical view
CPSD CryptoPro Secure Disk for BitLocker before version 7.7.4 uses a default TPM PCR policy that does not account for system boot state. Consequently, TPM-protected material may be unsealed through an unintended execution path or on different hardware. The record assigns CVSS 3.1 score 9.8 and CWE-1188.
Likely exposure
Exposure is limited to deployments running CPSD CryptoPro Secure Disk for BitLocker earlier than 7.7.4, particularly those relying on its default TPM PCR policy. The supplied record does not identify affected operating systems, deployment prevalence, or whether customized policies remain vulnerable.
Exploitation context
The source bundle does not report confirmed exploitation, and the CVE is not listed as KEV. Although the CVSS vector specifies network attackability, the description concerns TPM unsealing and boot or hardware state. The supplied evidence does not clarify practical access requirements, so remote exploitability should not be assumed.
Researcher notes
The core issue is insufficiently restrictive TPM authorization policy rather than a conventional BitLocker flaw. Important unanswered questions include the exact PCR selection, required physical or remote access, customized-policy exposure, and whether prior key compromise persists after upgrading. The CVSS network vector appears broader than the narrative and requires vendor clarification.
Mitigation direction
- Upgrade affected CPSD installations to version 7.7.4 or later.
- Review CPSD vendor guidance for required TPM policy changes or migration precautions.
- Prioritize devices protecting sensitive, regulated, or privileged-access data.
- Preserve recovery material and test disk accessibility before broad deployment.
Validation and detection
- Inventory CPSD installations and record exact deployed versions.
- Identify systems using the default TPM PCR policy.
- Confirm all affected installations were upgraded to version 7.7.4 or later.
- Verify updated systems boot normally and protected volumes remain accessible.
- Review vendor guidance for additional configuration-specific validation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-1188: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-59321 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.cpsd.at/blog/CVE reference, mitre
- https://i.blackhat.com/BH-USA-26/Presentations/US-26-Burch-The-Cost-of-Obscurity-Wednesday.pdfCVE reference, mitre
- https://i.blackhat.com/BH-USA-26/Presentations/US-26-Burch-The-Cost-of-Obscurity-wp.pdfCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Initialization of a Resource with an Insecure Default
Initialization of a Resource with an Insecure Default represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.