Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain pre-boot environment access
-
DeliveryAttach LUKS-encrypted volume
-
Exploitbootxsa.efi detects LUKS, skips integrity checks
-
ExecutionBoot system with tampered EFI binary
-
ImpactAccess encrypted data or persist malware
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Signature verification
|
| Exploitation Conditions | Exploitation requires all of the following: (1) the target system must have CPSD CryptoPro Secure Disk for BitLocker version prior to v7.7.4 installed as its pre-boot authentication component; (2) an attacker must be able to introduce a LUKS-encrypted volume into the system's boot device enumeration - this is achievable via physical attachment of a LUKS-formatted USB or disk, remote mounting of a LUKS image through an out-of-band management interface (BMC/IPMI/iDRAC virtual media), or OS-level compromise with the ability to configure and reboot to a LUKS device; (3) the LUKS volume must be present and detectable by bootxsa.efi during its execution phase. Once these conditions are met, the bypass is automatic - no further attacker interaction is required. The NVD CVSS AV:N/PR:N rating is inconsistent with this attack surface and should not be relied upon. What limits exploitation in practice: the product is niche with low deployment prevalence, physical or management-plane access is required, and no ready-made public exploit has been identified beyond the research disclosure. |
| Impact | The NVD-assigned CVSS vector (AV:N/AC:L/PR:N/UI:N) implies remote, unauthenticated, low-complexity exploitation - a characterization that is highly inconsistent with a UEFI bootloader attack surface. Bootloader components execute before OS networking stacks are initialized; realistic exploitation requires physical device access, access to an out-of-band management interface (BMC, iDRAC, iLO, IPMI) capable of mounting virtual media, or OS-level privilege with the ability to reboot and inject a LUKS-formatted disk image. The NVD CVSS vector is assessed as likely miscategorized and should not be used as the basis for risk triage. The EPSS score of 0.11% at the 1st percentile supports low automated or opportunistic exploitation probability, consistent with a niche product and an attack requiring physical proximity or privileged infrastructure access. There is no CISA KEV listing. The Black Hat USA 2026 disclosure ('The Cost of Obscurity,' Burch) does elevate risk for targeted scenarios: nation-state and advanced persistent threat actors targeting encrypted laptop fleets or high-security endpoints now have public research to build from. For organizations not running this specific product, risk is zero. |
| Exploit ScenarioDerived | An attacker with physical access to a laptop protected by CryptoPro Secure Disk for BitLocker attaches a LUKS-formatted USB drive before system power-on. When bootxsa.efi executes, it detects the LUKS volume and enters the flawed code path, bypassing all CryptoPro file integrity checks. The attacker's pre-staged tampered boot binary - which would normally fail integrity verification - loads and executes, granting access to BitLocker key material or establishing a persistent pre-OS backdoor. The Black Hat USA 2026 whitepaper by Burch provides research-grade technical detail that materially aids exploit construction. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 13, 2026
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.
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.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
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.
Know when Jwt Attack gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
Lifecycle Timeline
3DescriptionCVE.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.
Executive ViewAI
CryptoPro Secure Disk for BitLocker versions before v7.7.4 contain a critical boot-stage integrity bypass that allows attackers with LUKS-encrypted volume access to disable EFI security checks, enabling unauthorized firmware modification and malware persistence. No public exploit has been identified at time of analysis; however, Black Hat 2026 research disclosure substantially lowers the barrier to exploitation, and the absence of a vendor-released patch creates unmitigated risk for affected organizations.
No vendor-released patch identified at time of analysis. Interim mitigations include: (1) enforce BIOS/UEFI password protection and Secure Boot configuration; (2) disable legacy boot, USB boot, and external media boot in BIOS/UEFI settings; (3) implement physical access controls and surveillance for affected devices; (4) enable and monitor UEFI/EFI event logs for unauthorized boot changes; (5) centralize and protect BitLocker recovery keys with audit logging; (6) restrict administrative and network access to boot infrastructure and BitLocker management systems.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Jwt Attack
View allWhy is Microsoft republishing a CVE from 2013? We are republishing CVE-2013-3900 in the Security Update Guide to update
Authentication bypass in SimpleHelp 5.5.15 and prior (plus 6.0 pre-release builds) allows remote unauthenticated attacke
Authentication bypass in WSO2 API Manager and related components (Universal Gateway, Traffic Manager, API Control Plane,
Authentication bypass in Fortinet FortiOS, FortiProxy, and FortiSwitchManager allows unauthenticated remote attackers to
ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS
Security feature bypass in Microsoft .NET (shipped via Visual Studio 2022 17.12/17.14 and Visual Studio 2026 18.7) lets
ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS
The package jsrsasign before 10.5.25 are vulnerable to Improper Verification of Cryptographic Signature when JWS or JWT
Authentication and authorization bypass in fast-jwt 6.2.0 through 6.2.4 (npm, NearForm) lets a remote, unauthenticated a
A library injection vulnerability exists in Microsoft Teams (work or school) 24046.2813.2770.1094 for macOS. Rated criti
A library injection vulnerability exists in the WebView.app helper app of Microsoft Teams (work or school) 24046.2813.27
A library injection vulnerability exists in the com.microsoft.teams2.modulehost.app helper app of Microsoft Teams (work
EUVD-2025-210717
GHSA-p473-hhhj-xhf5
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB