{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-26959 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-26959 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-26959 is a high-severity code injection vulnerability in Alex4SSB ADB-Explorer, published on 19 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-26959 and fix it if it is affected.\n\nWhat it is: CVE-2026-26959 is a high-severity code injection vulnerability in Alex4SSB ADB-Explorer, published on 19 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-26959 in the wild and no public exploit code.\n\nAffected product: Alex4SSB ADB-Explorer. 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-26959/ (Markdown: https://insights.sbomify.com/CVE-2026-26959/index.md)","id":"CVE-2026-26959","markdown":"https://insights.sbomify.com/CVE-2026-26959/index.md","name":"CVE-2026-26959","record":{"aliases":["GHSA-gcgv-2jq7-74rp"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"ADB Explorer","requires_auth":"none","summary":"Attackers can execute arbitrary code by tricking users into launching ADB Explorer with a malicious configuration file pointing to a rogue binary.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-829","name":"Inclusion of Functionality from Untrusted Control Sphere"}],"description":"ADB Explorer is a fluent UI for ADB on Windows. Versions 0.9.26020 and below fail to validate the integrity or authenticity of the ADB binary path specified in the ManualAdbPath setting before executing it, allowing arbitrary code execution with the privileges of the current user. An attacker can exploit this by crafting a malicious App.txt settings file that points ManualAdbPath to an arbitrary executable, then convincing a victim to launch the application with a command-line argument directing it to the malicious configuration directory. This vulnerability could be leveraged through social engineering tactics, such as distributing a shortcut bundled with a crafted settings file in an archive, resulting in RCE upon application startup. Thus issue has been fixed in version 0.9.26021.","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":"ADB Explorer Vulnerable to RCE via Insufficient Input Validation","id":"CVE-2026-26959","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"node-tar has Arbitrary File Read/Write via Hardlink Target Escape Through Symlink Chain in Extraction","id":"CVE-2026-26960"},"packages":[],"prev":{"headline":"filippo.io/edwards25519 MultiScalarMult produces invalid results or undefined behavior if receiver is not the identity","id":"CVE-2026-26958"},"products":["ADB-Explorer"],"published":"2026-02-19","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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-20","vendors":["Alex4SSB"]},"summary":"Attackers can execute arbitrary code by tricking users into launching ADB Explorer with a malicious configuration file pointing to a rogue binary.","url":"https://insights.sbomify.com/CVE-2026-26959/"}