CVE-2025-59326
Unsigned code execution via temporary files in CryptoPro Secure Disk (<7.7.4).
Is CVE-2025-59326 being exploited?
Not confirmed. CVE-2025-59326 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.45% probability of exploitation in the next 30 days.
How severe is CVE-2025-59326?
CVE-2025-59326 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-59326?
Yes. A fix has been recorded for CVE-2025-59326. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-59326 affect?
CVE-2025-59326 affects CryptoPro Secure Disk for BitLocker < 7.7.4, Windows endpoints with CryptoPro Secure Disk installed, BitLocker deployments using CPSD. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2025-59326?
Upgrade to CryptoPro Secure Disk v7.7.4+, restrict execution from temp files, block writable temp mounts until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Allows execution of unsigned binaries from temp files, enabling arbitrary code execution and potential privilege escalation on affected Windows endpoints.
Immediate action required