# CVE-2026-123268: libyal libvmdk Extent Data File libvmdk_extent_table.c libvmdk_extent_table_get_extent_data_file_path memory corruption


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-123268, GHSA-5hxv-qxwp-44j8, UBUNTU-CVE-2026-123268

## What is CVE-2026-123268?

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

### Official description

A security vulnerability has been detected in libyal libvmdk up to 3fdd7839758e9f44ef95e1dfccde8552b860a4fc. Affected is the function libvmdk_extent_table_get_extent_data_file_path of the file libvmdk/libvmdk_extent_table.c of the component Extent Data File Handler. The manipulation leads to memory corruption. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. The identifier of the patch is 175d3fc0a0b961f362f16e7560a6169d7213e16b. Applying a patch is the recommended action to fix this issue.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-123268 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123268 is a medium-severity vulnerability in libyal libvmdk, published on 5 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123268 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-123268/ (Markdown: https://insights.sbomify.com/CVE-2026-123268/index.md)
```

## Sources

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

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