Code execution via untrusted ADB binary path
Published Feb 19, 2026 · Updated Feb 19, 2026
Code execution in ADB Explorer 0.9.26020 and earlier allows attackers to run an arbitrary executable through a crafted settings path. AdbHelper.CheckAdbVersion passes ManualAdbPath from App.txt to ADBService.VerifyAdbVersion, which starts that file without integrity or authenticity validation. Exploitation requires a user to launch the application with an argument selecting the malicious configuration directory, and the payload runs with that user's privileges.
Summary
What happened
Code execution in ADB Explorer 0.9.26020 and earlier allows attackers to run an arbitrary executable through a crafted settings path. AdbHelper.CheckAdbVersion passes ManualAdbPath from App.txt to ADBService.VerifyAdbVersion, which starts that file without integrity or authenticity validation. Exploitation requires a user to launch the application with an argument selecting the malicious configuration directory, and the payload runs with that user's privileges.
The record
- CVE
- CVE-2026-26959
- Published
- Feb 19, 2026
- Updated
- Feb 19, 2026
- Vendor
- Alex4SSB
- Product
- ADB Explorer
- Classifications
- CWE-829, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 19, 2026CVE publishedPublication date reported by the CVE source.
- Feb 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.9.26021
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Crafted App.txt proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo