cve.bz

CVE-2026-116260 Double Free

5.5 mediumEPSS 0.3%

Medium (5.5). EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
A weakness has been identified in libimobiledevice up to 1.4.0. This issue affects the function service_receive of the file src/afc.c of the component AFC Service. Executing a manipulation can lead to double free. The attack may be performed from remote. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Severity

CVSS 4.0

5.5 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

CVSS 3.1

7.3 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS
0.3% (unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 22nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-10-31. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
CWE-415 Double Free
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-116260 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116260?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116260?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-116260 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14libimobiledeviceno fix listedDEBIAN-CVE-2026-116260
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morelibimobiledeviceno fix listedUBUNTU-CVE-2026-116260
Red Hatenterprise_linux:8::appstreamlibimobiledevice, libimobiledevice-debuginfo, libimobiledevice-debugsource and 1 more0:1.2.0-18.el8_10RHSA-2026:98105
Red Hatenterprise_linux:8::crblibimobiledevice, libimobiledevice-devel, libimobiledevice-debuginfo and 2 more0:1.2.0-18.el8_10RHSA-2026:98105
AlmaLinux8libimobiledevice, libimobiledevice-devel1.2.0-18.el8_10ALSA-2026:98105
Rocky Linux8libimobiledevice0:1.2.0-18.el8_10RLSA-2026:98105

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat has rated this vulnerability as having an Important severity impact because memory corruption from double-free conditions can be triggered over the network without authentication, potentially resulting in arbitrary code execution or service disruption. In standard Red Hat Enterprise Linux deployments, libimobiledevice is primarily utilized in workstation or desktop environments for managing Apple mobile devices rather than in headless server installations. Exploitation requires an active connection exchanging data with an untrusted or malicious iOS endpoint over the Apple File Conduit service.

Red Hat's mitigation

If Apple device connectivity is not required, remove the optional `libimobiledevice` package to eliminate exposure:

# dnf remove libimobiledevice

Warning: Removing `libimobiledevice` may remove dependent desktop components such as `gvfs-afc` or related GNOME packages, which disables iOS device integration in graphical environments. Terminal access and server functionality remain fully usable.

--- CME Mitigation Guidance (2026-11-02) ---

Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to remove the libimobiledevice package or block untrusted network connections to the Apple File Conduit service: upgrade to the fixed Libimobiledevice builds, which apply the documented input check, closing all 2 injection vectors (manipulated AFC service network traffic, crafted responses from an untrusted iOS endpoint). Until patched, this is only a concern on Linux systems with libimobiledevice version 1.4.0 or earlier managing Apple mobile devices — Headless server installations not utilizing Apple mobile device management are unaffected — so Remove libimobiledevice if iOS connectivity is unnecessary, and avoid exchanging data with untrusted or malicious endpoints over the Apple File Conduit service. As a compensating measure, Randomize userspace memory layout to prevent reliable address resolution during heap corruption, Enforce SELinux policy to confine the execution domain of the libimobiledevice process, Deploy endpoint detection agents to detect anomalous process behavior and crash artifacts, Use eBPF runtime monitoring to detect shell spawns or abnormal system calls, Block unauthorized physical USB endpoint connections from untrusted iOS devices, and Enforce non-executable heap memory to prevent code execution within corrupted pages. These controls limit blast radius and contain exploitation, but they do not fix the underlying double-free defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-101 ASLR (Address Space Layout Randomization) (medium)

ProductPackageStateAdvisory
Red Hat Enterprise Linux 6libimobiledeviceNot affected
Red Hat Enterprise Linux 7libimobiledeviceAffected
Red Hat Enterprise Linux 8libimobiledeviceAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-116260.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-119 (12).

References

Check your stackJSON