Quick answers
- Is CVE-2026-116737 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116737 being exploited in the wild.
- How severe is CVE-2026-116737?
- Medium severity, with a CVSS score of 6.1, published 26 October 2026.
- Which products and versions are affected?
- Libyal Libphdi through 20260902.
- Is there a fix for CVE-2026-116737?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-116737 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-116737?
- Check whether you run Libyal Libphdi at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The libphdi_data_files_get_extent_data_file_path function uses the directory prefix length instead of the basename length when reading extent file paths, resulting in a heap out-of-bounds read. An attacker can construct a Parallels disk image descriptor with a long directory prefix and short basename to trigger the vulnerability via network or local file access. This may cause a denial of service or information disclosure.
Affected products
- libyal libphdi through 20260902
Timeline
- 2026-10-26: disclosed