How to Fix CVE-2026-27615: Path traversal: 'uncsharename' (windows unc share) in ADB-Explorer

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-27615 is a path traversal: 'uncsharename' (windows unc share) in Alex4SSB ADB-Explorer. The fix is to apply the vendor patch noted below.

What is CVE-2026-27615?

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 use 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. The CVSS base score is 8.8 (High), which puts this in the upper risk band and warrants a fast patch cycle. The official advisory is at https://github.com/Alex4SSB/ADB-Explorer/security/advisories/GHSA-3f27-jp2g-hwhr.

Am I affected?

Check the version of ADB-Explorer you are running and compare it against the Affected row above (ADB-Explorer < Beta 0.9.26022). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:

# Linux package check
dpkg -s adb-explorer 2>/dev/null | grep -i ^Version
rpm -q adb-explorer 2>/dev/null
command -v adb-explorer >/dev/null && adb-explorer --version 2>/dev/null

# Windows (PowerShell)
Get-Package -Name "*ADB-Explorer*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "ADB-Explorer" 2>$null

How to fix CVE-2026-27615

Upgrade ADB-Explorer to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian

sudo apt-get update
sudo apt-get install --only-upgrade adb-explorer
dpkg -s adb-explorer | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux

sudo dnf upgrade --refresh adb-explorer -y
# or for older releases:
sudo yum update adb-explorer -y
rpm -q adb-explorer

SUSE / openSUSE

sudo zypper refresh
sudo zypper update adb-explorer
rpm -q adb-explorer

Complete PowerShell remediation script (Windows)

# Fix script for CVE-2026-27615 affecting ADB-Explorer
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-27615-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*ADB-Explorer*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\adb-explorer-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\ADB-Explorer" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "ADB-Explorer" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "ADB-Explorer"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)

#!/usr/bin/env bash
# Fix script for CVE-2026-27615 affecting ADB-Explorer
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-27615-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s adb-explorer 2>/dev/null | grep -i ^Version || echo "adb-explorer not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q adb-explorer || echo "adb-explorer not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-27615-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/adb-explorer /etc/adb-explorer.d /etc/adb-explorer.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y adb-explorer
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y adb-explorer
elif command -v yum >/dev/null; then
    yum update -y adb-explorer
elif command -v zypper >/dev/null; then
    zypper --non-interactive update adb-explorer
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s adb-explorer 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q adb-explorer
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)

# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)

New-NetFirewallRule -DisplayName "Block-CVE-2026-27615" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-27615"

Disable the affected service (Linux)

sudo systemctl stop adb-explorer 2>/dev/null || true
sudo systemctl disable adb-explorer 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.

# Linux
dpkg -s adb-explorer 2>/dev/null | grep -i ^Version
rpm -q adb-explorer 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true

# Windows
Get-Package -Name "*ADB-Explorer*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Related fixes

Other vulnerabilities in the same area that are worth patching alongside this one:

• How to Fix CVE-2026-26306: Critical Vulnerability in OM Workspace (Windows Edition) — Critical Vulnerability in OM Workspace (Windows Edition)
• How to Fix CVE-2026-20771: Critical Vulnerability in Intel(R) QAT software drivers for Windows — Critical Vulnerability in Intel(R) QAT software drivers for Windows
• How to Fix CVE-2026-3000: Cwe-494 download of code without integrity check in IDExpert Windows Logon Agent , Cwe-494 download of code without integrity check in IDExpert Windows Logon Agent
• How to Fix CVE-2026-23863: Improper Neutralization of Null Byte or NUL Character (CWE-158) , Improper Neutralization of Null Byte or NUL Character (CWE-158)
• How to Fix CVE-2026-1232: Authentication Bypass in Privilege management for Windows , Authentication Bypass in Privilege management for Windows

Is CVE-2026-27615 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-27615?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-27615?

8.8 (High). Vector: 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.

Where is the official advisory for CVE-2026-27615?

The vendor advisory is at https://github.com/Alex4SSB/ADB-Explorer/security/advisories/GHSA-3f27-jp2g-hwhr. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-27615.

References

• Official vendor advisory: https://github.com/Alex4SSB/ADB-Explorer/security/advisories/GHSA-3f27-jp2g-hwhr
• NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27615
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*