Live › vulnerability › CVE-2026-116259
Go to dashboardA flaw in the afc_get_device_info_key function of libimobiledevice up to 1.4.0 lets a manipulated Value argument corrupt memory. A local attacker can use the public exploit to crash the process or possibly run code.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 11:29 UTC. All times on this page are UTC.
Systems that have libimobiledevice 1.4.0 or earlier installed, usually desktops or build hosts that talk to iPhones and iPads through the AFC service. Servers without iOS device tooling are unlikely to be exposed. unknown for exact trigger paths beyond the local vector described.
No product ranges from the sources yet.
ideviceinfo --version or the package manager, and see whether it is 1.4.0 or earlier.afc.c in the source tree still contains the unchecked handling of the Value argument in afc_get_device_info_key.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
A security flaw has been discovered in libimobiledevice up to 1.4.0. This vulnerability affects the function afc_get_device_info_key of the file src/afc.c of the component Device Info Handler. Performing a manipulation of the argument Value results in memory corruption. The attack requires a local approach. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
This page as .md · .json · in your agent: get_signal("CVE-2026-116259")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.