Skip to main content

CryptoPro Secure Disk CVE-2025-59327

| EUVDEUVD-2025-210717 HIGH
Improper Verification of Cryptographic Signature (CWE-347)
2026-08-12 mitre GHSA-p473-hhhj-xhf5
7.5
CVSS 3.1 · Vendor: mitre
Share

Severity by source

Vendor (mitre) PRIMARY
7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
vuln.today AI
6.0 MEDIUM

Pre-boot EFI execution context requires physical or privileged management-plane access (AV:L, PR:H); both confidentiality and integrity are fully compromised when all boot integrity checks are bypassed.

3.1 AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
4.0 AV:L/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (mitre).

CVSS VectorVendor: mitre

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

4
Analysis Generated
Aug 13, 2026 - 16:24 vuln.today
CVSS changed
Aug 13, 2026 - 16:22 NVD
7.5 (HIGH)
CVE Published
Aug 12, 2026 - 00:00 cve.org
HIGH 7.5
CVE Published
Aug 12, 2026 - 00:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

In CPSD CryptoPro Secure Disk for Bitlocker before v7.7.4, bootxsa.efi fails to properly validate LUKS encryption and, if encryption is present, all CryptoPro file integrity checks are skipped.

AnalysisAI

Boot-stage integrity bypass in CPSD CryptoPro Secure Disk for BitLocker before v7.7.4 allows an attacker who can present a LUKS-encrypted volume during the pre-boot phase to cause bootxsa.efi to skip all CryptoPro file integrity checks, enabling execution of tampered EFI boot components. Publicly disclosed at Black Hat USA 2026 with an accompanying whitepaper, substantially raising the bar for exploit development. No CISA KEV listing and EPSS at the 1st percentile indicate no observed mass exploitation, but the research-quality disclosure significantly reduces attacker effort for targeted campaigns against affected endpoints.

Technical ContextAI

bootxsa.efi is the UEFI-phase integrity module of CryptoPro Secure Disk for BitLocker, a pre-boot authentication and full-disk encryption product by Austrian vendor CPSD. Its function is to cryptographically verify the integrity of CryptoPro boot-stage components before control passes to BitLocker or the OS loader. The root cause maps to CWE-347 (Improper Verification of Cryptographic Signature): when bootxsa.efi detects the presence of LUKS (Linux Unified Key Setup) disk encryption, it takes a code path that unconditionally skips the entire integrity check pipeline rather than executing it independently of the LUKS-detection branch. This is a logic flaw - the LUKS-detection conditional short-circuits the integrity gate instead of treating it as a separate, mandatory step. NVD CPE data is unresolved (cpe:2.3:a:n/a:n/a), so product enumeration relies entirely on the CVE description and the vendor blog at cpsd.at/blog.

RemediationAI

Upgrade CPSD CryptoPro Secure Disk for BitLocker to version 7.7.4 or later, the confirmed vendor-released patch version per the CVE description. Consult the vendor advisory at https://www.cpsd.at/blog/ for upgrade procedures and release notes. Until patching is complete, restrict physical access to affected endpoints - this is the primary compensating control given the pre-boot attack surface. Additionally, tightly control or disable out-of-band management interfaces (BMC, iDRAC, iLO, IPMI) to prevent virtual media mounting that could introduce a LUKS volume without physical presence; note that disabling these interfaces may affect remote server management workflows. Enforcing UEFI Secure Boot policies at the firmware level provides partial defense by limiting which EFI binaries can execute, but does not address the logic flaw within the CryptoPro module itself. Eliminating LUKS-formatted volumes from the boot environment (if operationally feasible) removes the triggering condition, though this may break legitimate Linux dual-boot or cross-platform disk configurations.

CVE-2013-3900 MEDIUM
5.5 Dec 11

Why is Microsoft republishing a CVE from 2013? We are republishing CVE-2013-3900 in the Security Update Guide to update

CVE-2026-48558 CRITICAL POC
9.5 Jun 12

Authentication bypass in SimpleHelp 5.5.15 and prior (plus 6.0 pre-release builds) allows remote unauthenticated attacke

CVE-2025-59718 CRITICAL
9.8 Dec 09

Authentication bypass in Fortinet FortiOS, FortiProxy, and FortiSwitchManager allows unauthenticated remote attackers to

CVE-2025-25291 CRITICAL POC
9.3 Mar 12

ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS

CVE-2025-25292 CRITICAL POC
9.3 Mar 12

ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS

CVE-2022-25898 CRITICAL POC
9.8 Jul 01

The package jsrsasign before 10.5.25 are vulnerable to Improper Verification of Cryptographic Signature when JWS or JWT

CVE-2024-42004 CRITICAL POC
9.8 Dec 18

A library injection vulnerability exists in Microsoft Teams (work or school) 24046.2813.2770.1094 for macOS. Rated criti

CVE-2024-41145 CRITICAL POC
9.8 Dec 18

A library injection vulnerability exists in the WebView.app helper app of Microsoft Teams (work or school) 24046.2813.27

CVE-2024-41138 CRITICAL POC
9.8 Dec 18

A library injection vulnerability exists in the com.microsoft.teams2.modulehost.app helper app of Microsoft Teams (work

CVE-2024-45409 CRITICAL POC
9.8 Sep 10

The Ruby SAML library is for implementing the client side of a SAML authorization. Rated critical severity (CVSS 9.8), t

CVE-2022-35929 CRITICAL POC
9.8 Aug 04

cosign is a container signing and verification utility. Rated critical severity (CVSS 9.8), this vulnerability is remote

CVE-2022-31053 CRITICAL POC
9.8 Jun 13

Biscuit is an authentication and authorization token for microservices architectures. Rated critical severity (CVSS 9.8)

Share

CVE-2025-59327 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy