CryptoPro Secure Disk CVE-2025-59322

The attacker must be able to trigger a decryption error within the CryptoPro Secure Disk processing path - either by submitting malformed or invalid input to a service interface, or by inducing conditions (such as a key mismatch or invalid CBC IV) that cause the decryption routine to fail. The vendor-supplied CVSS vector (AV:N/AC:L/PR:N/UI:N) asserts network-reachable, unauthenticated exploitation with low complexity; however, this is inconsistent with the typical operational model of disk encryption middleware, which performs inherently local volume-mounting operations. Defenders must verify whether a network-facing component of CryptoPro Secure Disk is exposed in their specific deployment - this is the determining factor for whether remote unauthenticated exploitation is realistic or whether local system access is the true prerequisite. No specific non-default configuration, BitLocker policy, or operating system version is stated as a prerequisite beyond running a version earlier than v7.7.4. Exploitation is not limited by scope change: the impact is confined to the vulnerable system's encrypted volume data (C:H, I:N, A:N).

The vendor-supplied CVSS base score of 7.5 (High) and vector AV:N/AC:L/PR:N/UI:N describe an unauthenticated, low-complexity, network-exploitable path - but this vector is in tension with the inherent locality of disk-mounting operations; defenders should independently verify whether a network-accessible service component of CryptoPro Secure Disk is exposed in their environment before accepting the AV:N/PR:N framing as authoritative. EPSS is very low at 0.17% (6th percentile), indicating that mass exploitation has not emerged, consistent with the absence of a CISA KEV listing. However, the Black Hat 2026 public disclosure means the technical approach is now documented in open sources, and even a mid-sized municipal IT team in koszalin relying on this software as its sole data-at-rest control layer should treat patching as urgent given the maximal confidentiality impact - a triggered error leaves the entire protected volume readable without cryptographic barrier. SSVC technical impact is total for confidentiality; there is no integrity or availability impact. Automating exploitation depends on whether the decryption error condition can be reliably triggered remotely, which the public presentation materials may clarify but which is not confirmed in currently available structured CVE data.

An attacker capable of triggering a decryption error in CryptoPro Secure Disk - for example by submitting malformed input to a network-accessible service interface or by corrupting volume metadata to induce a key-mismatch condition - causes the software to mount the target encrypted volume as plaintext rather than rejecting the operation. The attacker then reads sensitive files directly from what should have been a cryptographically protected volume, with no further exploitation steps required. The Black Hat 2026 presentation materials, including the whitepaper at https://i.blackhat.com/BH-USA-26/Presentations/US-26-Burch-The-Cost-of-Obscurity-wp.pdf, are publicly available and document the technical approach in detail.