Skip to content
Fencer Vulns
low 3.5

CVE-2026-116261 json

libimobiledevice AFC File afc.c afc_file_open out-of-bounds

published 2026-10-26 14 d ago modified 2026-11-02 6 d ago also EUVD-2026-109778

cvss
3.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 9%
public exploits
0
none known

Summary

A security vulnerability has been detected in libimobiledevice up to 1.4.0. Impacted is the function afc_file_open of the file src/afc.c of the component AFC File Handler. The manipulation of the argument bytes leads to out-of-bounds read. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-116261 updated cvss 3.5

libimobiledevice: libimobiledevice: Information disclosure via out-of-bounds read in AFC file handler

  • Red Hat Enterprise Linux 6 libimobiledevice-python, libimobiledevice 0.9.7-4.el6
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 7 libimobiledevice-utils, libimobiledevice-python, libimobiledevice 0.9.7-4.el6 Red Hat Enterprise Linux 8 libimobiledevice 0.9.7-4.el6
    affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
6 d ago

Exploit prediction

0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • bohmid-com.vercel.app https://bohmid-com.vercel.app/#/article/blog-afc-writeup referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 5.1 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
CNA 3.1 3.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N/E:P/RL:X/RC:C
CNA 3.0 3.5 CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N/E:P/RL:X/RC:C
CNA 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N/E:POC/RL:ND/RC:C
CNA 4.0 2.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
CNA 3.1 3.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
CNA 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N

Affected products

  • n/a libimobiledevice

Classification

Weakness
  • CWE-125 Out-of-bounds Read
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.