{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116259 exists.","fix":"No fix has been published for CVE-2026-116259 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-116259 is a medium-severity vulnerability in libimobiledevice, published on 26 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-116259 and fix it if it is affected.\n\nWhat it is: CVE-2026-116259 is a medium-severity vulnerability in libimobiledevice, published on 26 Oct 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116259 exists.\n\nAffected product: libimobiledevice. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-116259/ (Markdown: https://insights.sbomify.com/CVE-2026-116259/index.md)","id":"CVE-2026-116259","markdown":"https://insights.sbomify.com/CVE-2026-116259/index.md","name":"CVE-2026-116259","record":{"aliases":["DEBIAN-CVE-2026-116259","GHSA-3p74-qv2f-x33f","UBUNTU-CVE-2026-116259"],"analysis":null,"analysis_generated_by":null,"assigner":"VulDB","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"A security flaw has been discovered in libimobiledevice up to 1.4.0. This vulnerability affects the function afc_get_device_info_key of the file src/afc.c of the component Device Info Handler. Performing a manipulation of the argument Value results in memory corruption. The attack requires a local approach. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"libimobiledevice Device Info afc.c afc_get_device_info_key memory corruption","id":"CVE-2026-116259","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"libimobiledevice AFC Service afc.c service_receive double free","id":"CVE-2026-116260"},"packages":[],"prev":{"headline":"libimobiledevice AFC afc.c heap-based overflow","id":"CVE-2026-116258"},"products":["libimobiledevice"],"published":"2026-10-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-26","vendors":["n/a"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-116259/"}