# CVE-2026-26208: ADB Explorer Vulnerable to Remote Code Execution via Insecure Deserialization

> An attacker can execute arbitrary code by tricking a user into opening a malicious settings file in ADB Explorer.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Feb 2026
- **Updated:** 13 Feb 2026
- **Also known as:** GHSA-49qx-wpxj-p4mh

## What is CVE-2026-26208?

CVE-2026-26208 is a high-severity unsafe deserialization vulnerability in Alex4SSB ADB-Explorer, published on 13 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.

### Official 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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-26208?


## How do I fix CVE-2026-26208?

No fix has been published for CVE-2026-26208 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-26208 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26208 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-26208 and fix it if it is affected.

What it is: CVE-2026-26208 is a high-severity unsafe deserialization vulnerability in Alex4SSB ADB-Explorer, published on 13 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26208 exists.

Affected product: Alex4SSB ADB-Explorer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-26208/ (Markdown: https://insights.sbomify.com/CVE-2026-26208/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26208
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26208
- OSV: https://osv.dev/vulnerability/CVE-2026-26208

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-26208/
Summaries are generated and may contain mistakes; the official description above is the record.