Quick answers
- Is CVE-2026-116259 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116259 being exploited in the wild.
- How severe is CVE-2026-116259?
- Medium severity, with a CVSS score of 5.3, published 26 October 2026.
- Which products and versions are affected?
- Libimobiledevice up to 1.4.0.
- Is there a fix for CVE-2026-116259?
- 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-116259 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-116259?
- Check whether you run Libimobiledevice 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 memory corruption vulnerability exists in the afc_get_device_info_key function in src/afc.c of libimobiledevice's Device Info Handler component. The flaw is triggered by manipulation of the Value argument passed to this function. Exploitation requires local access to the affected device; the vulnerability has been publicly disclosed and proof-of-concept exploits are available.
Affected products
- libimobiledevice libimobiledevice up to 1.4.0
Timeline
- 2026-10-26: disclosed
- exploited: Proof-of-concept exploits released publicly