Skip to main content
Menu
CVEs

CVE

Dockhand path traversal in stack relocate enables directory moves

Affects Finsys Dockhand 1.0.54 and earlier for users holding the stacks:edit permission. Fixed in 1.0.55.

CVE-2026-130791Published Updated Summary written by a model

8.6HighCNA
Exploited
No known exploitation
Fix
Fixed in 1.0.55
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. User holds stacks:edit permission Dockhand version 1.0.54 or earlier

Summary

Finsys Dockhand before 1.0.55 contains a path traversal vulnerability that allows users with stacks:edit permission to move arbitrary server directories by supplying a crafted oldDir parameter. Attackers can send POST requests to /api/stacks/[name]/relocate with an unvalidated source path to relocate directories into stack paths, disrupting services and exposing their contents.

Who should check

Teams running Dockhand 1.0.54 or earlier, especially self-hosted instances where users hold stacks:edit permission

“Dockhand v1.0.53 allows any user with stacks:edit permission”

github.com

cve.now Index

17Pcve.now Index 17 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.6/10CVSS 8.6
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 24 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    User holds stacks:edit permission Dockhand version 1.0.54 or earlier
  • Upgrade to a fixed version: 1.0.55.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130791 (Finsys Dockhand before 1.0.55 Path Traversal via Stack Relocate oldDir Parameter), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130791 (entry last updated 2026-11-18):
Affected:
- Finsys dockhand: fixed in 1.0.55
Fixed versions: 1.0.55.
Conditions (all must be true for the bug to be hit):
- User holds stacks:edit permission (source: https://github.com/Finsys/dockhand/security/advisories/GHSA-c6m5-4xrm-4x39)
- Dockhand version 1.0.54 or earlier (source: https://github.com/Finsys/dockhand/security/advisories/GHSA-c6m5-4xrm-4x39)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130791 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130791 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Finsys/dockhand/security/advisories/GHSA-c6m5-4xrm-4x39
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130791
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130791"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Finsys dockhand

    fixed in 1.0.55

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · Finsys/dockhand · Advisory GHSA-c6m5-4xrm-4x39
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130791
RecordNVD · CVE-2026-130791

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130791

Is CVE-2026-130791 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A user with the stacks:edit permission can use the Stack Relocate oldDir parameter to move arbitrary directories on the server. This can disrupt services and expose the contents of the displaced directories.Source: github.com

Which versions are affected by CVE-2026-130791?

dockhand: before 1.0.55.Source: cve.now feed data

Am I affected, and how do I check?

Dockhand version 1.0.54 and earlier is affected, for accounts holding the stacks:edit permission. Check the installed Dockhand version and which accounts hold that permission.Source: github.com

How do I fix CVE-2026-130791?

Upgrade Dockhand to version 1.0.55 or later, which is the fixed version.Source: github.com

More CVEs