Skip to main content
VulnerabilityPublished

CVE-2026-26208: Alex4SSB ADB-Explorer · Deserialization of Untrusted Data

Affects Alex4SSB ADB-ExplorerSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High · fixed in 0.9.26020 : patch Alex4SSB ADB-Explorer soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.9.26020
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Alex4SSBADB-ExplorerAffected
  • =< Beta 0.9.26020
Fixed in–

AI-suggested

  1. Immediately update ADB-Explorer to Beta 0.9.26020 or later, where the vulnerability is fixed.
  2. Restrict write permissions on the App.txt settings file to trusted users only to prevent unauthorized modification.
  3. Implement endpoint security controls to detect and prevent unauthorized file changes and monitor for suspicious application launches.
  4. Educate users about the risks of launching untrusted applications or files and enforce least privilege principles to limit the impact of potential exploitation.
  5. Use application whitelisting to prevent execution of unauthorized or modified versions of ADB-Explorer.
  6. Regularly audit and monitor systems for signs of compromise, focusing on Windows endpoints used for mobile device management.
  7. Consider isolating development or device management environments to reduce exposure.
  8. If updating is not immediately possible, disable or restrict usage of ADB-Explorer until patched.

Description

ADB Explorer is a fluent UI for ADB on Windows. Prior to Beta 0.9.26020, ADB Explorer is vulnerable to Insecure Deserialization leading to Remote Code Execution. The application attempts to deserialize the App.txt settings file using Newtonsoft.Json with TypeNameHandling set to Objects. This allows an attacker to supply a crafted JSON file containing a gadget chain (e.g., ObjectDataProvider) to execute arbitrary code when the application launches and subsequently saves its settings. This vulnerability is fixed in Beta 0.9.26020.

References

Community reviews

Loading reviews…