Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach Dockhand API over network
-
DeliverySend PUT /api/users/<id>.js
-
ExploitAuth hook skips check on .js path
-
ExecutionHandler fails open, resets password
-
PersistLog in as admin
-
ImpactFull instance takeover
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Alternate path authentication
|
| Exploitation Conditions | No special conditions beyond network reachability of the Dockhand HTTP API: exploitation works against default configurations of any Dockhand instance before 1.0.45. The specific trigger is any request whose path ends in a static-asset extension (e.g. .js), which causes the global authentication hook to skip the auth check even for /api/* routes; combined with user-mutation handlers that fail open for unauthenticated callers, a PUT to /api/users/<id>.js resets an arbitrary user's (including admin's) password. The only genuine limiting factor is network exposure - an instance whose API is not reachable by the attacker (internal-only, firewalled, or behind an authenticating reverse proxy) is not exploitable; no authentication, user interaction, or non-default setting is required. |
| Impact | Every available signal points to maximum, real-world risk. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes network-reachable, low-complexity exploitation requiring no privileges and no user interaction, and this is fully consistent with the description: an unauthenticated PUT to /api/users/<id>.js resets any account's password. The CWE-288 (authentication bypass via alternate path) classification matches the described flaw exactly - the global auth hook treats any path ending in a static-asset extension as public, and the user-mutation handlers fail open. This is a priority issue, not a high-CVSS-but-low-risk paper cut: it yields direct admin account takeover with a single request. Tempering the urgency, no EPSS score, no KEV listing, and no POC flag were provided in the input, so there is no evidence of active exploitation or published exploit code at this time; the 10.0 reflects intrinsic severity, not demonstrated mass exploitation. The 4.0 subsequent-system impacts (SC:H/SI:H/SA:H) are plausible given that a compromised Dockhand admin typically controls Docker hosts/containers behind it, but the input does not confirm that downstream reach - treat it as vendor-scored rather than independently verified. |
| Exploit ScenarioDerived | An attacker who can reach the Dockhand web interface sends a single crafted PUT request to /api/users/<id>.js; because the path ends in .js the global auth hook skips authentication, and the fail-open user-mutation handler resets the targeted account's password. The attacker then logs in as the admin and takes full control of the Dockhand instance. No public exploit code was identified in the provided data, but the technique is trivially reproducible from the description. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Unauthenticated account takeover in Dockhand before 1.0.45 lets any remote attacker who can reach the HTTP API reset the password of the administrative or any other user account and seize it outright. The flaw chains two design failures: a global authentication hook that deliberately skips any request path ending in a static-asset extension such as .js - including paths under /api/ - and user-mutation handlers that fail open when no authenticated principal is present, so a single unauthenticated PUT to /api/users/<id>.js rewrites that user's credentials. No authentication, user interaction, or non-default configuration is required, and there is no public exploit code identified at time of analysis; the only real limiting factor is whether an attacker can reach the Dockhand API over the network, since the flaw is rated 10.0 (CVSS 4.0) and scores CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H on independent assessment. Vendor patching is available, making unpatched internet-facing instances the primary exposure.
RemediationAI
Apply the vendor-released patch: upgrade Dockhand to 1.0.45 or later, the first release outside the affected '<1.0.45' range, per the vendor advisory GHSA-r3mg-r5vm-3v6w (https://github.com/Finsys/dockhand/security/advisories/GHSA-r3mg-r5vm-3v6w); patch availability is confirmed by the vendor, so there is no need to accept residual risk on this issue. Because exploitation results in credential replacement rather than mere data disclosure, upgrading alone is insufficient - after patching, treat every account on a previously exposed instance as compromised: force password resets and revoke sessions/API tokens for all users, especially administrators, and review Dockhand logs for unauthenticated PUT requests to /api/users/ paths carrying a static-asset suffix such as .js, which is the exact exploitation signature. If immediate patching is impossible, the most effective compensating control is to stop the malicious request shape from reaching the application: add a reverse-proxy or WAF rule that rejects any request whose path begins with /api/ and ends in a static-asset extension (for example /^\/api\/.*\.(js|mjs|css|map|png|svg|ico)$/), which blocks the bypass without breaking legitimate front-end assets served from other paths - the trade-off being that the rule must be maintained as new asset extensions appear and that legitimate API paths with dotted identifiers could be caught if the pattern is written too broadly. Additionally, restrict Dockhand's API to trusted networks or place it behind an authenticating proxy, since the vulnerability is only reachable when the API is exposed; this limits blast radius but does not remediate the code flaw and may break remote management workflows. Do not rely on hiding the /api/users endpoints as a primary mitigation, as the bypass applies across all /api/* routes reached with the suffix trick.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause maps to CWE-288, Authentication Bypass Using an Alternate Path or Channel, combined with a fail-open authorization design. Dockhand's global auth hook is intended to permit unauthenticated access to static front-end assets (JavaScript, CSS and similar) so the login page can render, and it implements that allow-list by inspecting the request path suffix - for example treating anything ending in .js as a harmless asset. Because the check is a suffix match on the full path rather than a match on a normalized, decoded route prefix, it can be satisfied by appending a static-asset extension to an API route, so /api/users/<id>.js passes the hook as though it were a script file while still being routed to the users controller. The second defect is that the user-mutation handlers for those routes fail open: rather than rejecting an unauthenticated caller, they proceed with the mutation. Together these allow an unauthenticated PUT to /api/users/<id>.js under /api/ to perform a password change for an arbitrary account, giving full account takeover of the admin account and, by extension, of the Dockhand instance it manages. The affected technology is the Dockhand HTTP management API, and the EUVD affected-version range confirms all releases from 0 up to but excluding 1.0.45 are vulnerable.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Unauthenticated single-request admin takeover over the network with no user interaction gives AV:N/AC:L/PR:N/UI:N and full C/I/A; scope kept U as impact lands in the same application authority.
Primary rating from Vendor (vulncheck).
CVSS VectorVendor: vulncheck
Lifecycle Timeline
2DescriptionCVE.org
Dockhand before 1.0.45 contains an authentication bypass in which the global auth hook skips authentication for any path ending in a static-asset extension such as .js, including /api/* routes, and the user-mutation handlers fail open for unauthenticated callers. Unauthenticated remote attackers can send a PUT request to /api/users/<id>.js to reset the admin's or any user's password and take over the account.
Technical POC Analysis
The bug class is chained CWE-306 Missing Authentication for Critical Function plus CWE-863 Incorrect Authorization; the advisory also tags CWE-284/CWE-287.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
Organizations using Dockhand before version 1.0.45 are exposed to a maximum-severity account takeover issue that can hand complete control of the platform, including administrative accounts, to an unauthenticated remote party. The consequence is potential unauthorized access to sensitive data, loss of service integrity, and operational disruption across any internet-reachable deployment. Security leadership should treat this as an emergency patching and exposure-reduction priority.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-100465
GHSA-4xvp-4f97-666q
NVD
CVE.org
EPSS
Exploit-DB