CVE-2026-57169: Dockhand: Unauthenticated container exec via WebSocket upgrade

Published Oct 16, 2026
·
Updated

Dockhand is a Docker management application. Prior to 1.0.34, the in-browser container terminal endpoint /api/containers/<id>/exec does not enforce authentication on the WebSocket upgrade request. When an unauthenticated attacker has network reach to Dockhand, knows a target container ID, and targets a container with an interactive shell, the attacker can open a raw WebSocket terminal session and execute commands inside a known target container. This allows unauthenticated command execution inside the container, with possible host compromise when the container has sensitive mounts or privileged execution. This issue is fixed in version 1.0.34.

Affected Software

1 affected component
Dockhand Dockhand<1.0.34

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Dockhand to a version that resolves this vulnerability.

    Fixed in 1.0.34

Event History

Oct 16, 2026
CVE Published
via MITRE·04:13 PM
Data Sourced
via MITRE·04:13 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are practically exposed?

Dockhand deployments prior to 1.0.34 are exposed if an unauthenticated attacker can reach the Dockhand service over the network. Exploitation also requires the attacker to know a target container ID and for that container to have an interactive shell.

2

Does an attacker need valid Dockhand credentials or user interaction?

No. The WebSocket upgrade request to the container exec endpoint does not enforce authentication, so no credentials or user interaction are required.

3

What is the likely impact beyond the targeted container?

An attacker can execute commands in the targeted container through a raw WebSocket terminal session. Host compromise may be possible when that container has sensitive mounts or privileged execution.

4

What should be done if an immediate upgrade is not possible?

Restrict unauthenticated network access to the Dockhand service so untrusted attackers cannot reach it. Limiting exposure does not remove risk for any unauthenticated party that can still access the endpoint.

5

How can defenders determine whether they are affected?

Check whether Dockhand is running a version earlier than 1.0.34 and whether its container exec endpoint is reachable by unauthenticated network clients. Also identify containers with interactive shells, privileged execution, or sensitive mounts, as these are higher-impact targets.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203