libimobiledevice up to 1.4.0 Device Info src/afc.c afc_get_device_info_key value memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 2.99 |
Summary
A vulnerability described as problematic has been identified in libimobiledevice up to 1.4.0. This issue affects the function afc_get_device_info_key of the file src/afc.c of the component Device Info Handler. Executing a manipulation of the argument Value can lead to memory corruption.
This vulnerability appears as CVE-2026-116259. The attack requires local access. In addition, an exploit is available.
The vendor was contacted early about this disclosure but did not respond in any way.
Details
A vulnerability has been found in libimobiledevice up to 1.4.0 and classified as problematic. This vulnerability affects the function afc_get_device_info_key of the file src/afc.c of the component Device Info Handler. The manipulation of the argument value with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability.
The advisory is available at bohmid-com.vercel.app. This vulnerability was named CVE-2026-116259. The exploitation appears to be easy. Local access is required to approach this attack. Technical details and also a public exploit are known.
It is possible to download the exploit at bohmid-com.vercel.app. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-109775). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.0
VulDB Base Score: 5.3
VulDB Temp Score: 5.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
10/25/2026 Advisory disclosed10/25/2026 VulDB entry created
10/26/2026 VulDB entry last update
Sources
Advisory: bohmid-com.vercel.appStatus: Confirmed
CVE: CVE-2026-116259 (🔒)
GCVE (CVE): GCVE-0-2026-116259
GCVE (VulDB): GCVE-100-426298
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 10/25/2026 18:49Updated: 10/26/2026 15:30
Changes: 10/25/2026 18:49 (56), 10/26/2026 15:30 (1)
Complete: 🔍
Submitter: ahmed0000
Cache ID: 216::103
Submit
Accepted
- Submit #1009968: libimobiledevice fa0f79190142bc309307967c058f89c1b36eb6b8 - version 1.4.0 Memory corruption (by ahmed0000)
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.