Quick answers
- Is CVE-2026-116743 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116743 being exploited in the wild.
- How severe is CVE-2026-116743?
- Medium severity, with a CVSS score of 5.5, published 26 October 2026.
- Which products and versions are affected?
- Libyal Libmsiecf through 20260525.
- Is there a fix for CVE-2026-116743?
- 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-116743 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-116743?
- Check whether you run Libyal Libmsiecf 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
A double-free vulnerability exists in the libmsiecf_url_values_read_data() function that processes partial URL records from MSIE cache index.dat files. An attacker can craft a malicious cache file with an oversized unknown_offset field that triggers the double-free condition, leading to heap memory corruption. This vulnerability requires the victim to process a crafted index.dat file, resulting in denial of service to forensic tools.
Affected products
- libyal libmsiecf through 20260525
Timeline
- 2026-10-26: disclosed