CVE-2026-116258
Received Received - Intake

Heap-based Buffer Overflow in libimobiledevice

Vulnerability report for CVE-2026-116258, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-26

Last updated on: 2026-10-26

Assigner: VulDB

Description

A vulnerability was identified in libimobiledevice up to 1.4.0. This affects an unknown part of the file src/afc.c of the component AFC. Such manipulation leads to heap-based buffer overflow. The attack can be executed remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-26
Last Modified
2026-10-26
Generated
2026-10-26
AI Q&A
2026-10-26
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 5 associated CPEs
Vendor Product Version / Range
n/a libimobiledevice 1.0
n/a libimobiledevice 1.1
n/a libimobiledevice 1.2
n/a libimobiledevice 1.3
n/a libimobiledevice 1.4.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-119 The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
CWE-122 A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a heap-based buffer overflow in libimobiledevice up to version 1.4.0, specifically in the file src/afc.c of the AFC component. It allows remote attackers to execute arbitrary code or cause a denial of service by manipulating data in memory.

Detection Guidance

Detecting this vulnerability requires checking for vulnerable versions of libimobiledevice. Use commands like 'dpkg -l | grep libimobiledevice' on Debian-based systems or 'rpm -qa | grep libimobiledevice' on RPM-based systems to identify installed versions. If version 1.4.0 or earlier is found, the system is likely vulnerable.

Impact Analysis

An attacker could exploit this to crash applications, execute malicious code, or gain unauthorized access to data on systems using vulnerable versions of libimobiledevice. The exploit is publicly available, increasing the risk of real-world attacks.

Compliance Impact

This vulnerability could lead to unauthorized data access or disclosure, violating GDPR (data protection) and HIPAA (health data privacy) requirements. Organizations using vulnerable software may face compliance violations, fines, or legal consequences.

Mitigation Strategies

Immediately update libimobiledevice to the latest version beyond 1.4.0. If no update is available, consider disabling AFC services or restricting network access to affected systems. Monitor for unusual network traffic or system behavior as a potential sign of exploitation.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-116258. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart