CVE-2026-27615
Alex4Ssb Adb Explorer ≤ 0.9.26022
Raw 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-27615 is a high-severity Windows UNC Share (CWE-40) vulnerability in Alex4Ssb Adb Explorer. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Supply Chain Compromise (T1195); ranked at the 11th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SR-4 (Provenance) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-27615 affects ADB Explorer, a Windows graphical user interface for the Android Debug Bridge (ADB) tool, in versions prior to Beta 0.9.26022. The vulnerability stems from the application's acceptance of a Universal Naming Convention (UNC) path in the `ManualAdbPath` settings variable within its `App.txt` configuration file. This setting dictates the path to the ADB binary executed by the app, enabling an attacker to redirect it to a remote network share under their control. Assigned CWEs include CWE-40 (Path Equivalence: 'filename' attack) and CWE-829 (Signal Handler Race Condition), with a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), indicating high confidentiality, integrity, and availability impacts.
An attacker can exploit this flaw by social engineering a victim into launching ADB Explorer via a malicious shortcut that references a custom `App.txt` file—such as one embedded in a downloaded archive. Upon execution, the app loads the tampered settings, causing it to fetch and run an ADB binary from the attacker's UNC-controlled share. This grants remote code execution on the victim's machine at the privileges of the running user, with no prerequisite privileges for the attacker beyond victim interaction.
The GitHub security advisory (GHSA-3f27-jp2g-hwhr) confirms that updating to Beta 0.9.26022 resolves the issue by preventing UNC paths in the `ManualAdbPath` setting. Security practitioners should advise users to update immediately, verify settings files for tampering, and avoid running untrusted shortcuts or archives containing ADB Explorer.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-8596
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 6 hardening rules · 6 OS baselines
V14.2.3V3.5.6V9.1.3V15.3.2
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly rejects malformed or malicious UNC paths before they are resolved to unintended locations.
Requires documented, valid provenance for components, preventing acceptance of code from outside the trusted sphere.
Enforced access authorizations can limit damage from a traversed UNC path even if the path itself is accepted.
Implements detection and prevention of counterfeit or inauthentic components before they are integrated.
Establishes processes to identify and address supply-chain weaknesses that would allow untrusted functionality.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Pre-acquisition integrity/authenticity checks directly prevent inclusion of untrusted code.
Supply-chain program directly governs inclusion of third-party executable code.
Contractual requirements can mandate trusted sources and integrity checks for included functionality.
Supplier risk assessment explicitly covers risks from their products and libraries.
Critical-supplier assessment reduces risk of importing executable functionality from untrusted parties.
Secure SDLC practices directly prevent introduction of unsafe path-handling code such as UNC traversal.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
By requiring suppliers to propagate security requirements and to disclose component provenance, the control limits the inclusion of functionality obtained from untrusted third-party sources without oversight.
Security testing can discover and verify the absence of UNC-based path traversal vulnerabilities.
Network security controls can block or filter UNC paths that traverse outside approved shares.
Application security requirements can mandate input validation to reject malicious UNC paths.
Secure architecture principles include canonicalization and path-handling controls that prevent UNC traversal.
Secure coding standards directly require validation and sanitization of file paths including UNC shares.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248635 Executable search paths within the initialization files of all local interactive OL 8 users must only contain paths that resolve to the system default or the user's home directory. prevents CWE-829
Oracle Linux 9 (1 rule)
- V-271847 OL 9 must be configured so that executable search paths within the initialization files of all local interactive users must only contain paths that resolve to the system default or the users home directory. prevents CWE-829
RHEL 7 (1 rule)
- V-204477 The Red Hat Enterprise Linux operating system must be configured so that all local interactive user initialization files executable search paths contain only paths that resolve to the users home directory. prevents CWE-829
RHEL 8 (1 rule)
- V-230317 Executable search paths within the initialization files of all local interactive RHEL 8 users must only contain paths that resolve to the system default or the users home directory. prevents CWE-829
RHEL 9 (1 rule)
- V-258050 Executable search paths within the initialization files of all local interactive RHEL 9 users must only contain paths that resolve to the system default or the users home directory. prevents CWE-829
Windows 10 (1 rule)
- V-220737 Administrative accounts must not be used with applications that access the Internet, such as web browsers, or with potential Internet sources, such as email. prevents CWE-829