CVE-2026-134448 in Dockhand
Summary
by MITRE • 11/21/2026
Finsys Dockhand 1.0.7 before 1.0.57 contains a path traversal vulnerability that allows low-privileged users to read and write arbitrary files by setting an unvalidated envPath on a stack source. Attackers with stacks:edit permission can point envPath to files like /etc/shadow or SSH keys, then use GET or PUT on /api/stacks/[name]/env/raw to read or overwrite them.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The vulnerability identified in Finsys Dockhand versions prior to 1.0.57 represents a critical path traversal flaw that stems from insufficient validation of user-supplied input within the application's environment variable handling mechanism. Specifically, the software fails to properly sanitize or restrict the envPath parameter when processing requests related to stack sources. This lack of rigorous input validation allows an attacker with low-privileged access, specifically those possessing stacks:edit permissions, to manipulate file system paths in a manner that bypasses intended directory boundaries. By injecting relative path sequences such as dot-dot-slash into the envPath field, the application resolves these references against the server's root or current working directory rather than restricting them to an expected safe location. This architectural oversight effectively neutralizes any implicit security controls designed to isolate stack-specific data from sensitive system files.
The operational impact of this vulnerability is severe due to its potential for both information disclosure and remote code execution via credential theft. An attacker can leverage the GET method on the /api/stacks/[name]/env/raw endpoint to read arbitrary files stored on the host operating system. This includes highly sensitive data such as /etc/shadow, which contains password hashes, or SSH private keys that may be used for authentication across multiple systems within a network infrastructure. Conversely, by utilizing the PUT method on the same endpoint, an attacker can overwrite critical configuration files or inject malicious content into scripts executed during container initialization. This capability allows for persistent access and potential escalation of privileges if the overwritten file is subsequently read by a higher-privileged process or service account.
From a classification perspective, this vulnerability aligns with CWE-22: Improper Limitation of a Pathname to a Restricted Directory, which describes flaws where software does not properly neutralize special elements within a pathname that can cause the path to resolve to directories outside of the intended restricted directory. Furthermore, in terms of tactical behavior as defined by MITRE ATT&CK, this exploit maps directly to T1552: Unsecured Credentials, specifically under the sub-technique of direct access to credentials such as SSH keys or password files. The ability to read and write arbitrary files also touches upon T1083: File and Directory Discovery for reconnaissance purposes before executing more destructive actions like data exfiltration or system compromise.
Mitigation strategies must prioritize immediate patching to version 1.0.57 or later, where the developers have implemented proper input validation and path canonicalization checks. In addition to updating the software, administrators should enforce strict least-privilege principles by auditing user roles and ensuring that stacks:edit permissions are granted only to trusted individuals who require them for operational tasks. Network-level controls such as web application firewalls can provide a temporary layer of defense by detecting and blocking requests containing path traversal sequences like ../ or encoded variations thereof, although this should not be relied upon as the primary security control. Regular auditing of file system access logs is also recommended to detect any unauthorized attempts to read sensitive files via the API endpoints in question.