Skip to main content
CVE-2026-121448VulnerabilityPublished

Dockhand before 1.0.54 contains a path traversal vulnerability that allows authenticated users to read, overwrite, and

Affects dockhandSource GCVE Database

0
Compare
Authoritative record:CVE-2026-121448· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 1.0.54 soon.

Data as of 3 Nov 2026, 16:14 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.7
CNA (VulnCheck)CVSS 3.18.3
Affects
deployment variables. Dockhand before 1.0.54
Patch
Available – fixed in 1.0.54
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

What to do

Upgrade finsys/dockhand to 1.0.54.

Affected software

ProductAffectedFixed in
GitHubfinsys/dockhandpkg:github/finsys/dockhandOther threatsAffected
  • <1.0.54
Fixed in
  • 1.0.54

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Dockhand version 1.0.54. Users should upgrade to version 1.0.54 or later to remediate this vulnerability. No vendor advisory content is provided to indicate alternative mitigations or temporary fixes.

Description

Dockhand versions prior to 1.0.54 contain a path traversal vulnerability that allows authenticated users to read, overwrite, and delete .env files outside the intended stack root directory. This is achieved by double-encoding the stack name in API requests, enabling unauthorized access to sensitive environment files and potential manipulation of deployment variables.

References

Community reviews

Loading reviews…