Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-27115 is a high-severity Path Traversal (CWE-22) vulnerability in Alex4Ssb Adb Explorer. Its CVSS base score is 7.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 13th 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 AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — 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-27115 affects ADB Explorer, a Windows application providing a fluent user interface for the Android Debug Bridge (ADB). Versions 0.9.26020 and prior contain an unvalidated command-line argument vulnerability that enables recursive deletion of arbitrary directories on the Windows filesystem. The application accepts an optional path argument to specify a custom data directory but only verifies if the path exists, without further validation. During application startup and exit, the ClearDrag() method invokes Directory.Delete(dir, true) on every subdirectory of the provided path, allowing unintended file system modifications.
The vulnerability can be exploited by any attacker who tricks a user into launching ADB Explorer via a malicious shortcut (.lnk file), batch script, or similar mechanism that passes a critical directory—such as C:\Users\%USERNAME%\Documents—as the command-line argument. This requires local access to create the malicious launcher but relies on user interaction (UI:R) with no privileges (PR:N). Successful exploitation results in permanent recursive deletion of all subdirectories within the targeted path, bypassing the Windows Recycle Bin and causing high integrity (I:H) and availability (A:H) impacts with a CVSS v3.1 base score of 7.1.
Mitigation is available in ADB Explorer version 0.9.26021, which addresses the issue through changes detailed in the project's GitHub commit (f7554690b1f68c6066c12aa45aec60303bca545b), release notes (v0.9.26021), and security advisory (GHSA-rg2h-2p33-rxcr). Security practitioners should advise users to update immediately and avoid launching the application from untrusted shortcuts or scripts. The vulnerability maps to CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) and CWE-73 (External Control of File Name or Path).
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-8364
Vulnerability Data
ADB Explorer is a fluent UI for ADB on Windows. Versions 0.9.26020 and below have an unvalidated command-line argument that allows any user to trigger recursive deletion of arbitrary directories on the Windows filesystem. ADB Explorer accepts an optional path…
more
argument to set a custom data directory, but only check whether the path exists. The ClearDrag() method calls Directory.Delete(dir, true) on every subdirectory of that path at both application startup and exit. An attacker can craft a malicious shortcut (.lnk) or batch script that launches ADB Explorer with a critical directory (e.g. C:\Users\%USERNAME%\Documents) as the argument, causing permanent recursive deletion of all its subdirectories. Any user who launches ADB Explorer via a crafted shortcut, batch file, or script loses the contents of the targeted directory permanently (deletion bypasses the Recycle Bin). This issue has been fixed in version 0.9.26021.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces the intended directory access authorizations that path traversal would otherwise bypass.
Input validation directly neutralizes special path elements before pathname construction occurs.
Least privilege reduces the impact of any unauthorized file access obtained via traversal.
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.
Secure SDLC practices include input validation and path sanitization that eliminate this weakness.
Least-privilege file authorization directly limits damage from externally controlled paths.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
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.
Security testing in development catches path traversal via static/dynamic analysis.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
Application security requirements include rules for safe file handling and canonicalization.
Secure architecture principles require least-privilege file access and directory isolation.
Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.
Information access restriction limits which files an application may read or write.