# CVE-2025-59319: CPSD CryptoPro Secure Disk for Bitlocker before v7.7.4 fails to certify the integrity of the intended boot partition and selects the first p


- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 12 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-5vmp-mmw3-vwr3

## What is CVE-2025-59319?

CVE-2025-59319 is a high-severity vulnerability in n/a, published on 12 Aug 2026. 

### Official description

CPSD CryptoPro Secure Disk for Bitlocker before v7.7.4 fails to certify the integrity of the intended boot partition and selects the first partition index matching a hardcoded type value. A crafted Linux partition could be inserted ahead of this intended target, allowing for code execution in the context of high privilege.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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


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

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

## Is CVE-2025-59319 being exploited?

There is no known exploitation of CVE-2025-59319 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59319 is a high-severity vulnerability in n/a, published on 12 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2025-59319 in the wild and no public exploit code.

Affected product: n/a. 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-59319/ (Markdown: https://insights.sbomify.com/CVE-2025-59319/index.md)
```

## Sources

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

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