# CVE-2026-116258: libimobiledevice AFC afc.c heap-based overflow


- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-116258, GHSA-pvmf-fpv3-m5qh, UBUNTU-CVE-2026-116258

## What is CVE-2026-116258?

CVE-2026-116258 is a medium-severity vulnerability in libimobiledevice, published on 26 Oct 2026. 

### Official 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.

Weakness: CWE-122 (Heap-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2026-116258?


## How do I fix CVE-2026-116258?

No fix has been published for CVE-2026-116258 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-116258 being exploited?

There is no known exploitation of CVE-2026-116258 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-116258 and fix it if it is affected.

What it is: CVE-2026-116258 is a medium-severity vulnerability in libimobiledevice, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116258 in the wild and no public exploit code.

Affected product: libimobiledevice. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-116258/ (Markdown: https://insights.sbomify.com/CVE-2026-116258/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-116258
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-116258
- OSV: https://osv.dev/vulnerability/CVE-2026-116258

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-116258/
Summaries are generated and may contain mistakes; the official description above is the record.