A Weakness Has Been Identified In Libimobiledevice Up To 140 Cve 2026 116260 4a774db87cd10b39

Exploited in the wild Exploited : no evidence on record. Not in CISA KEV and no source reports exploitation

Exploited in the wild Exploited : no evidence on record.

Not in CISA KEV and no source reports exploitation

Observed by OffSeq Mirage Seen by Mirage : no evidence on record. No attack traffic recorded by OffSeq Mirage sensors

Observed by OffSeq Mirage Seen by Mirage : no evidence on record.

No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab) , CVSS vector , the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026 .

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

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 this disclosure but did not respond in any way.

CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer (opens in a new tab) Class weakness Likelihood of exploit: High 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. MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness. Requirements · Language Selection Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Architecture and Design · Libraries or Frameworks Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Operation · Build and Compilation · Environment Hardening Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index… OWASP Cheat Sheets XML Security (opens in a new tab) Mass Assignment (opens in a new tab) OWASP ASVS 4.0.3 V13.3.1 (opens in a new tab) V5.1.4 (opens in a new tab) V5.1.3 (opens in a new tab) Attack patterns Buffer Overflow via Environment Variables (opens in a new tab) Overflow Buffers (opens in a new tab) Client-side Injection-induced Buffer Overflow (opens in a new tab) Filter Failure through Buffer Overflow (opens in a new tab) MIME Conversion (opens in a new tab) From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

Class weakness Likelihood of exploit: High

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.

MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.

Requirements · Language Selection Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.

Requirements · Language Selection

Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.

Architecture and Design · Libraries or Frameworks Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.

Architecture and Design · Libraries or Frameworks

Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.

Operation · Build and Compilation · Environment Hardening Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…

Operation · Build and Compilation · Environment Hardening

Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…

XML Security (opens in a new tab)

Mass Assignment (opens in a new tab)

V13.3.1 (opens in a new tab)

V5.1.4 (opens in a new tab)

V5.1.3 (opens in a new tab)

Buffer Overflow via Environment Variables (opens in a new tab)

Overflow Buffers (opens in a new tab)

Client-side Injection-induced Buffer Overflow (opens in a new tab)

Filter Failure through Buffer Overflow (opens in a new tab)

MIME Conversion (opens in a new tab)

From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

nvd.nist.gov /vuln/detail/CVE-2026-116260 (opens in a new tab)

bohmid-com.vercel.app (opens in a new tab)

vuldb.com /cve/CVE-2026-116260 (opens in a new tab)

vuldb.com /submit/1009969 (opens in a new tab)

vuldb.com /vuln/426299 (opens in a new tab)

vuldb.com /vuln/426299/cti (opens in a new tab)