ADB-Explorer: UNC Path Support in ManualAdbPath Leads to Remote Code Execution (RCE)
ADB Explorer is a fluent UI for ADB on Windows. In versions prior to Beta 0.9.26022, ADB-Explorer allows the `ManualAdbPath` settings variable, which determines the path of the ADB binary to be executed, to be set to a Universal Naming Convention (UNC) path in the application's settings file. This allows an attacker to set the binary's path to point to a remote network resource, hosted on an attacker-controlled network share, thus granting the attacker full control over the binary being executed by the app. An attacker may leverage this vulnerability to execute code remotely on a victim's machine with the privileges of the user running the app. Exploitation is made possible by convincing a victim to run a shortcut of the app that points to a custom `App.txt` settings file, which sets `ManualAdbPath` (for example, when downloaded in an archive file). Version Beta 0.9.26022 fixes the issue.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-27615
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 02:44 UTC · Revision 1
Source evidence
ADB-Explorer: UNC Path Support in ManualAdbPath Leads to Remote Code Execution (RCE)
core-osv · Original sourcePublished 25 Feb 2026, 02:33 UTC
ADB Explorer is a fluent UI for ADB on Windows. In versions prior to Beta 0.9.26022, ADB-Explorer allows the `ManualAdbPath` settings variable, which determines the path of the ADB binary to be executed, to be set to a Universal Naming Convention (UNC) path in the application's settings file. This allows an attacker to set the binary's path to point to a remote network resource, hosted on an attacker-controlled network share, thus granting the attacker full control over the binary being executed by the app. An attacker may leverage this vulnerability to execute code remotely on a victim's machine with the privileges of the user running the app. Exploitation is made possible by convincing a victim to run a shortcut of the app that points to a custom `App.txt` settings file, which sets `ManualAdbPath` (for example, when downloaded in an archive file). Version Beta 0.9.26022 fixes the issue.
osv:CVE-2026-27615
Complete source record
{
"id": "74e41ffdbc712cfdddf3cbd05377759320787495a5136853dc3d0a4f5f811541",
"url": "https://osv.dev/vulnerability/CVE-2026-27615",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "ADB-Explorer: UNC Path Support in ManualAdbPath Leads to Remote Code Execution (RCE)",
"summary": "ADB Explorer is a fluent UI for ADB on Windows. In versions prior to Beta 0.9.26022, ADB-Explorer allows the `ManualAdbPath` settings variable, which determines the path of the ADB binary to be executed, to be set to a Universal Naming Convention (UNC) path in the application's settings file. This allows an attacker to set the binary's path to point to a remote network resource, hosted on an attacker-controlled network share, thus granting the attacker full control over the binary being executed by the app. An attacker may leverage this vulnerability to execute code remotely on a victim's machine with the privileges of the user running the app. Exploitation is made possible by convincing a victim to run a shortcut of the app that points to a custom `App.txt` settings file, which sets `ManualAdbPath` (for example, when downloaded in an archive file). Version Beta 0.9.26022 fixes the issue.",
"evidence": "osv:CVE-2026-27615",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-27615",
"aliases": [
"CVE-2026-27615",
"GHSA-3f27-jp2g-hwhr"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/alex4ssb/adb-explorer",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "84937d171a29daa3753d2a8e83b50a323ee1fe89"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:alex4ssb:adb_explorer:*:*:*:*:*:windows:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "0.9.26022"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"versions": [
"v0.9.26021",
"v0.9.26020",
"v0.9.26011",
"v0.9.26010",
"v0.9.25111",
"v0.9.25110",
"v0.9.25102",
"v0.9.25101r",
"v0.9.25101",
"v0.9.25100",
"v0.9.25090",
"v0.9.25080",
"v0.9.25070",
"v0.9.25066",
"v0.9.25060",
"v0.9.25052",
"v0.9.25051",
"v0.9.25050",
"v0.9.25022",
"v0.9.25021",
"v0.9.25020",
"v0.8.24121",
"v0.8.24120",
"v0.8.24060",
"v0.8.24030",
"v0.8.23120",
"v0.8.23090",
"v0.8.23060",
"v0.8.23050",
"v0.8.23030",
"v0.7.9001",
"v0.7.9",
"v0.7.7",
"v0.7.6",
"v0.7.5",
"v0.7.4",
"v0.7.3",
"v0.7.2",
"v0.7.1",
"v0.7.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-27615.json"
}
}
],
"modified": "2026-10-28T02:30:49.100424719Z",
"provider": "osv",
"references": [
"https://github.com/Alex4SSB/ADB-Explorer/security/advisories/GHSA-3f27-jp2g-hwhr",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/27xxx/CVE-2026-27615.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-27615"
],
"provider_metadata": {
"cwe_ids": [
"CWE-40",
"CWE-829"
],
"cna_assigner": "GitHub_M",
"unresolved_ranges": [
{
"extracted_events": [
{
"range": [
{
"fixed": "Beta0.9.26022"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
}
]
}
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/27xxx/CVE-2026-27615.json"
}
},
"related_cves": [
{
"value": "CVE-2026-27615",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 517463,
"published_at": "2026-02-25T02:33:53.553+00:00"
}