Unsigned code execution via temporary filesystem policy gap
Published Aug 12, 2026 · Updated Aug 12, 2026
Integrity policy bypass in CPSD CryptoPro Secure Disk for Bitlocker before 7.7.4 allows attackers to execute unsigned code. The product's IMA policy omits temporary file systems from appraisal, so executables staged there are not subjected to signature enforcement. Exploitation requires the ability to place and launch code from an affected temporary file system; the demonstrated consequence is a code-integrity bypass rather than a network entry point.
Summary
What happened
Integrity policy bypass in CPSD CryptoPro Secure Disk for Bitlocker before 7.7.4 allows attackers to execute unsigned code. The product's IMA policy omits temporary file systems from appraisal, so executables staged there are not subjected to signature enforcement. Exploitation requires the ability to place and launch code from an affected temporary file system; the demonstrated consequence is a code-integrity bypass rather than a network entry point.
The record
- CVE
- CVE-2025-59326
- Published
- Aug 12, 2026
- Updated
- Aug 12, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
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
No CVSS assessment is available in this record.
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
No sourced classifications are available.
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