# CVE-2026-107634: Dislocker through 0.7.3 Heap Out-of-Bounds Read via BitLocker Metadata Dataset Size

> Attackers can cause crashes or disclose heap memory by crafting malicious BitLocker volume images processed by the Dislocker tool.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 Oct 2026
- **Updated:** 10 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-107634, GHSA-gj99-98mp-m7r6, UBUNTU-CVE-2026-107634

## What is CVE-2026-107634?

CVE-2026-107634 is a medium-severity memory corruption vulnerability in Aorimn dislocker, published on 8 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Dislocker through 0.7.3 contains a heap out-of-bounds read vulnerability in get_dataset() and get_next_datum() that never validate dataset and datum sizes against the metadata allocation. Attackers can craft a BitLocker volume image with inflated dataset or datum sizes that, when opened or mounted, crashes dislocker or discloses adjacent heap memory.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-107634?


## How do I fix CVE-2026-107634?

Apply the vendor's patch.

## Is CVE-2026-107634 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107634 and fix it if it is affected.

What it is: CVE-2026-107634 is a medium-severity memory corruption vulnerability in Aorimn dislocker, published on 8 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-107634 in the wild and no public exploit code.

Affected product: Aorimn dislocker. 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-2026-107634/ (Markdown: https://insights.sbomify.com/CVE-2026-107634/index.md)
```

## Sources

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

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