Quick answers
- Is CVE-2026-116260 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116260 being exploited in the wild.
- How severe is CVE-2026-116260?
- High severity, with a CVSS score of 7.3, published 26 October 2026.
- Which products and versions are affected?
- Libimobiledevice up to 1.4.0.
- Is there a fix for CVE-2026-116260?
- 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-116260 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-116260?
- 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 double free vulnerability exists in the service_receive function of src/afc.c in the AFC Service component of libimobiledevice up to 1.4.0. The vulnerability can be triggered remotely by manipulating input to the service_receive function. Successful exploitation leads to memory corruption that can result in denial of service or code execution.
Affected products
- libimobiledevice libimobiledevice up to 1.4.0
Timeline
- 2026-10-26: disclosed: Public disclosure of CVE-2026-116260
- exploited: Exploit made available publicly