# CVE-2025-10010: Integrity Validation Bypass in CryptoPro Secure Disk for BitLocker

> Attackers with physical access can bypass integrity checks to execute arbitrary code as root in the pre-boot Linux environment.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Feb 2026
- **Updated:** 12 Mar 2026
- **Also known as:** GHSA-58j5-qr69-3544

## What is CVE-2025-10010?

CVE-2025-10010 is a medium-severity vulnerability in CPSD IT SERVICES GMBH CryptoPro Secure Disk for BitLocker, published on 24 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The CPSD CryptoPro Secure Disk application boots a small Linux operating system to perform user authentication before using BitLocker to decrypt the Windows partition. The system is located on a separate unencrypted partition which can be reached by anyone with access to the hard disk.

Multiple checks are performed to validate the integrity of the Linux operating system and the CryptoPro Secure Disk application files. When files are changed an error is shown on system start. One of the checks is the Linux kernel's Integrity Measurement Architecture (IMA). It was identified that configuration files are not validated by the IMA and can then (if not checked by other measures) be changed. This allows an attacker to execute arbitrary code in the context of the root user and enables an attacker to e.g., plant a backdoor and access data during execution.

Weakness: CWE-353 (Missing Support for Integrity Check)

## Which versions are affected by CVE-2025-10010?

It affects 1 product.


Products: Cpsd Cryptopro Secure Disk.

## How do I fix CVE-2025-10010?

No fix has been published for CVE-2025-10010 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-10010 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10010 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10010 and fix it if it is affected.

What it is: CVE-2025-10010 is a medium-severity vulnerability in CPSD IT SERVICES GMBH CryptoPro Secure Disk for BitLocker, published on 24 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10010 exists.

Affected product: CPSD IT SERVICES GMBH CryptoPro Secure Disk for BitLocker. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-10010/ (Markdown: https://insights.sbomify.com/CVE-2025-10010/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-10010
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-10010
- OSV: https://osv.dev/vulnerability/CVE-2025-10010

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-10010/
Summaries are generated and may contain mistakes; the official description above is the record.