Arbitrary code execution via unsafe App.txt deserialization
Published Feb 13, 2026 · Updated Feb 13, 2026
Insecure deserialization in ADB Explorer before Beta 0.9.26020 allows attackers to execute arbitrary code through a crafted App.txt settings file. App.xaml.cs globally enables Newtonsoft.Json TypeNameHandling.Objects, allowing App.txt to instantiate attacker-selected .NET types and gadget chains. Exploitation requires a user to launch ADB Explorer against an attacker-supplied settings directory and close it, triggering code execution with that user's privileges.
Summary
What happened
Insecure deserialization in ADB Explorer before Beta 0.9.26020 allows attackers to execute arbitrary code through a crafted App.txt settings file. App.xaml.cs globally enables Newtonsoft.Json TypeNameHandling.Objects, allowing App.txt to instantiate attacker-selected .NET types and gadget chains. Exploitation requires a user to launch ADB Explorer against an attacker-supplied settings directory and close it, triggering code execution with that user's privileges.
The record
- CVE
- CVE-2026-26208
- Published
- Feb 13, 2026
- Updated
- Feb 13, 2026
- Vendor
- Alex4SSB
- Product
- ADB Explorer
- Classifications
- CWE-502, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 13, 2026CVE publishedPublication date reported by the CVE source.
- Feb 13, 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=< Beta 0.9.26020
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
- GHSA-49qx-wpxj-p4mh proof of conceptproof of concept · unverified
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