Quick answers
- Is CVE-2026-111147 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111147 being exploited in the wild.
- How severe is CVE-2026-111147?
- Medium severity, with a CVSS score of 6.1, published 15 October 2026.
- Which products and versions are affected?
- Libyal Libesedb through 20260704.
- Is there a fix for CVE-2026-111147?
- 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-111147 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-111147?
- Check whether you run Libyal Libesedb 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 vulnerability is a heap out-of-bounds read in the libesedb_record_get_multi_value() function caused by unbounded multi-value offset tables, allowing an attacker to read past allocated buffers. The attack requires providing a crafted ESE/EDB database file processed by tools like esedbexport, with no authentication or user interaction needed beyond opening the file. An attacker can leak adjacent heap memory or cause a denial of service crash.
Affected products
- Libyal libesedb through 20260704
Timeline
- 2026-10-15: disclosed