cve.bz

CVE-2026-116258 Heap-based Buffer Overflow

2.1 lowEPSS 0.2%

Low (2.1). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

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

CVSS 3.1

6.3 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
CWE-122 Heap-based Buffer Overflow
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-116258 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116258?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116258?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-116258 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-116258
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morelibimobiledeviceno fix listedUBUNTU-CVE-2026-116258

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate severity because exploitation requires an established Apple File Conduit session with a connected iOS device, limiting exposure to active file transfer interactions. In Red Hat Enterprise Linux environments, libimobiledevice is not configured as an exposed listening network service and is used client-side primarily within desktop installations to communicate with paired mobile hardware. A malicious or compromised device sending malformed responses can cause the client process to crash or corrupt memory, but it cannot compromise the system remotely without an active user connection.

Red Hat's mitigation

Avoid connecting untrusted iOS devices to the host system.

If Apple device communication features are not required, remove the optional libimobiledevice package:

# dnf remove libimobiledevice

Warning: Removing libimobiledevice may remove dependent desktop integration packages (such as gvfs-afc or related GNOME utilities) and disable Apple device interoperability. Systems remain fully accessible and manageable via terminal and command line.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 6libimobiledeviceNot affected
Red Hat Enterprise Linux 7libimobiledeviceFix deferred
Red Hat Enterprise Linux 8libimobiledeviceFix deferred

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-116258.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

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