CVE-2026-134453 in Dockhandinfo

Summary

by MITRE • 11/21/2026

Dockhand before 1.0.50 contains an improper access control vulnerability that allows authenticated unprivileged users to read restricted data by querying API endpoints lacking RBAC checks. Attackers can access /api/users, /api/license, and /api/hawser/connect to obtain user emails and roles, the full license key, and environment details, while an invalid license grants all users admin rights.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Analysis

by VulDB Data Team • 11/21/2026

The vulnerability identified in Dockhand versions prior to 1.0.50 represents a critical failure in role-based access control mechanisms within the application's API layer. This flaw allows authenticated but unprivileged users to bypass intended security restrictions and access sensitive data that should be reserved for administrators or specific privileged roles. The root cause lies in the absence of proper authorization checks on several key API endpoints, specifically /api/users, /api/license, and /api/hawser/connect. In a secure implementation, these endpoints would verify not only that the user is authenticated but also that they possess the necessary permissions to perform the requested action or view the data. Instead, the application relies solely on authentication tokens without validating the associated role privileges, leading to an improper access control condition where any valid login can escalate their effective capabilities beyond what was granted during account creation.

The operational impact of this vulnerability is severe due to the nature of the exposed information and the secondary effect related to license validation logic. By querying /api/users, attackers can retrieve a list of user emails and roles, which facilitates further social engineering attacks or targeted phishing campaigns against other users within the organization. Accessing /api/license allows an attacker to extract the full license key associated with the instance, potentially enabling unauthorized deployment or resale of the software. Furthermore, the endpoint /api/hawser/connect exposes environment details that can aid in crafting more sophisticated exploits tailored to the specific infrastructure configuration. Beyond direct data exfiltration, a particularly dangerous aspect of this vulnerability is the behavior surrounding invalid licenses; if an attacker submits an invalid license key through these endpoints, the system erroneously grants all users administrative rights. This effectively bypasses any remaining security controls and provides full control over the application environment to anyone who can authenticate, regardless of their initial privilege level.

From a classification perspective, this vulnerability aligns with CWE-269, which describes Improper Privilege Assignment, as well as CWE-862, Missing Authorization, because the system fails to enforce access restrictions on resources accessible by authenticated users. In terms of adversary tactics, this behavior corresponds to ATT&CK technique T1078, Valid Accounts, where attackers leverage legitimate credentials to gain unauthorized access, and potentially T1539, Steal Web Session Cookie, if session tokens are also compromised through the exposed user data. The ability to escalate privileges by exploiting license validation logic further complicates remediation efforts, as it suggests a fundamental flaw in how the application handles state changes based on external inputs like license keys.

To mitigate this vulnerability, organizations running Dockhand versions earlier than 1.0.50 must immediately upgrade to version 1.0.50 or later, where these access control checks have been implemented. For environments that cannot be updated instantly due to operational constraints, temporary mitigations should include restricting network access to the API endpoints via firewall rules or reverse proxy configurations, ensuring that only trusted internal networks can reach them. Additionally, implementing strict input validation and error handling for license key submissions can help prevent the unintended privilege escalation associated with invalid licenses until a permanent patch is applied. Regular auditing of authentication and authorization logic across all API routes is recommended to ensure no other endpoints suffer from similar oversights in role verification processes.

Responsible

VulnCheck

Reservation

11/21/2026

Disclosure

11/21/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Do you need the next level of professionalism?

Upgrade your account now!