Skip to main content
Menu
CVEs

Dockhand code execution via PATH poisoning in stack deploy

Affects Dockhand up to 1.0.56 with authentication enabled and default RBAC roles, where a malicious binary can be placed in the PATH directory used by stack deploy. Fixed in 1.0.57.

CVE-2026-134452Published November 21, 2026, updated

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 1.0.57
Who is exposed
Specific setups only

Summary

Written by a model

Dockhand before 1.0.57 merges stack secret environment variables into the environment used to spawn docker compose during stack deploys without filtering reserved keys such as PATH. An authenticated attacker with stacks:edit permission can set PATH to a directory containing a malicious binary and trigger a deploy, executing arbitrary commands as the Dockhand server process user.

Who should check

Teams running Dockhand before 1.0.57 with stack deploys enabled, where users hold the stacks:edit permission

“Affecting dockhand < 1.0.57”

vulncheck.com

What to do

  1. Check whether your setup matches what the bug needs.

    Dockhand before 1.0.57 (affected versions up to 1.0.56) Attacker must also be able to write a malicious binary into the directory set as PATH (e.g. via a writable Docker volume or bind mount) Tested with authentication enabled and default RBAC roles
  2. Upgrade to a fixed version: 1.0.57.

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-134452 (Dockhand before 1.0.57 RCE via PATH Poisoning in Stack Deploy), 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-134452 (entry last updated 2026-11-21):
Affected:
- Finsys dockhand: fixed in 1.0.57
Fixed versions: 1.0.57.
Conditions (all must be true for the bug to be hit):
- Dockhand before 1.0.57 (affected versions up to 1.0.56) (source: https://www.vulncheck.com/advisories/dockhand-before-1.0.57-rce-via-path-poisoning-in-stack-deploy)
- Attacker must also be able to write a malicious binary into the directory set as PATH (e.g. via a writable Docker volume or bind mount) (source: https://github.com/Finsys/dockhand/security/advisories/GHSA-8fh8-h5v2-wmj4)
- Tested with authentication enabled and default RBAC roles (source: https://github.com/Finsys/dockhand/security/advisories/GHSA-8fh8-h5v2-wmj4)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134452 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134452 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-8fh8-h5v2-wmj4
- https://www.vulncheck.com/advisories/dockhand-before-1.0.57-rce-via-path-poisoning-in-stack-deploy
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-134452
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-134452"}.

Affected versions

cve.now Index

17Pof 100 · provisional · methodology v3
  • 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.7/10CVSS 8.7
  • 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

Timeline

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

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · Finsys/dockhand · Advisory GHSA-8fh8-h5v2-wmj4
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134452
RecordNVD · CVE-2026-134452
Other links 1
Linkvulncheck.com · advisories/dockhand-before-1.0.57-rce-via-path-poisoning-in-stack-deploy

Questions about CVE-2026-134452

Is CVE-2026-134452 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?

During stack deploy, Dockhand can run a malicious binary placed in a directory listed in PATH. The binary runs with the privileges of the Dockhand server process user.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134452?

dockhand: before 1.0.57.

Source: cve.now feed data

Am I affected, and how do I check?

Dockhand versions before 1.0.57, up to 1.0.56, were tested with authentication enabled and default RBAC roles. The setup also needs a way to write a binary into the PATH directory, such as a writable Docker volume or bind mount. Check the installed Dockhand version and whether authEnabled is set to true.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134452?

Upgrade Dockhand to version 1.0.57 or later.

Source: vulncheck.com, github.com

No corrections so far. Something wrong on this page? Report an error.