# CVE-2026-123269: libyal libvmdk Descriptor File libvmdk_descriptor_file.c libvmdk_descriptor_file_read_header out-of-bounds


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Nov 2026
- **Updated:** 6 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-123269, GHSA-327v-6wgx-g787, UBUNTU-CVE-2026-123269

## What is CVE-2026-123269?

CVE-2026-123269 is a medium-severity vulnerability in libyal libvmdk, published on 6 Nov 2026. 

### Official description

A vulnerability was detected in libyal libvmdk. Affected by this vulnerability is the function libvmdk_descriptor_file_read_header of the file libvmdk/libvmdk_descriptor_file.c of the component Descriptor File Parser. The manipulation results in out-of-bounds read. The attack must be initiated from a local position. The exploit is now public and may be used. The patch is identified as 175d3fc0a0b961f362f16e7560a6169d7213e16b. It is best practice to apply a patch to resolve this issue.

Weakness: CWE-125 (Out-of-bounds Read), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-123269 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123269 is a medium-severity vulnerability in libyal libvmdk, published on 6 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123269 exists.

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

## Sources

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

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