{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-116260 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-116260 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-116260 is a medium-severity vulnerability in libimobiledevice, published on 26 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-116260 and fix it if it is affected.\n\nWhat it is: CVE-2026-116260 is a medium-severity vulnerability in libimobiledevice, published on 26 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-116260 in the wild and no public exploit code.\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-116260/ (Markdown: https://insights.sbomify.com/CVE-2026-116260/index.md)","id":"CVE-2026-116260","markdown":"https://insights.sbomify.com/CVE-2026-116260/index.md","name":"CVE-2026-116260","record":{"aliases":["DEBIAN-CVE-2026-116260","GHSA-37ch-7vcr-862r","UBUNTU-CVE-2026-116260"],"analysis":null,"analysis_generated_by":null,"assigner":"VulDB","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-415","name":"Double Free"},{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"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 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":"none_known"},"has_fix":false,"headline":"libimobiledevice AFC Service afc.c service_receive double free","id":"CVE-2026-116260","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 File afc.c afc_file_open out-of-bounds","id":"CVE-2026-116261"},"packages":[],"prev":{"headline":"libimobiledevice Device Info afc.c afc_get_device_info_key memory corruption","id":"CVE-2026-116259"},"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-26","vendors":["n/a"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-116260/"}