Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-110255 Overview
CVE-2026-110255 is a response-disclosing server-side request forgery (SSRF) vulnerability in Finsys Dockhand versions prior to 1.0.43. Authenticated users can supply crafted repository URL and stackfile values to the templates compose endpoint, causing the server to fetch arbitrary URLs on their behalf. The fetched content is returned in the compose response field, enabling attackers to read internal service data and cloud metadata responses. This exposure can leak credentials, access tokens, and instance identity material. The weakness is tracked under CWE-918.
Critical Impact
Authenticated attackers can retrieve content from internal services and cloud metadata endpoints, exposing credentials and tokens that enable further lateral movement.
Affected Products
- Finsys Dockhand versions prior to 1.0.43
- Dockhand API templates/compose endpoint
- Deployments exposing Dockhand to authenticated users with repository or stackfile submission rights
Discovery Timeline
- 2026-10-13 - CVE CVE-2026-110255 published to NVD
- 2026-10-13 - Last updated in NVD database
Technical Details for CVE-2026-110255
Vulnerability Analysis
Dockhand accepts stack template definitions that reference remote resources through repository URL and stackfile parameters. The templates compose endpoint fetches these resources server-side to assemble a Docker Compose definition. The server does not restrict the destination of the outbound request, so any URL supplied by an authenticated user is retrieved from the application host.
Because the compose response field returns the fetched content back to the caller, Dockhand functions as a response-disclosing SSRF proxy. Attackers can target http://169.254.169.254/ on AWS, GCP, and Azure to recover instance identity documents, IAM credentials, and bootstrap tokens. Requests to loopback addresses or internal service IPs reveal admin interfaces, Redis, databases, and internal HTTP APIs that trust the Dockhand host.
Root Cause
The root cause is missing validation on user-supplied URLs before the server issues an outbound HTTP request. Dockhand does not enforce an allowlist of repository hosts, reject private IP ranges, block link-local addresses, or validate schemes. The response is then reflected to the caller without filtering, converting a classic SSRF into a data exfiltration primitive.
Attack Vector
Exploitation requires authenticated access to the Dockhand API. The attacker submits a stack template whose repository URL points at an internal target such as http://169.254.169.254/latest/meta-data/iam/security-credentials/ or an internal management service. Dockhand retrieves the response and places its body in the compose response field returned to the attacker. See the GitHub Security Advisory GHSA-f2mx-74xq-g4p9 and the VulnCheck SSRF Advisory for Dockhand for additional technical context.
// Example exploitation flow (described in prose)
// 1. Authenticate to the Dockhand API.
// 2. POST a stack template to the compose endpoint with repository URL
// set to an internal or metadata endpoint.
// 3. Read the fetched content from the compose response field.
// Verified code examples are not published; see the vendor advisory.
Detection Methods for CVE-2026-110255
Indicators of Compromise
- Outbound HTTP requests from the Dockhand host to 169.254.169.254, 127.0.0.1, or RFC1918 ranges originating from the templates compose workflow.
- API audit records showing repository URL or stackfile values containing internal hostnames, loopback addresses, or cloud metadata URLs.
- Unexpected use of recovered IAM credentials or short-lived tokens shortly after Dockhand template compose activity.
Detection Strategies
- Alert on Dockhand process network connections targeting link-local, loopback, or private address space.
- Review web server and application logs for POST requests to the templates compose endpoint containing non-standard repository schemes or hosts.
- Correlate authentication events with sudden spikes in outbound requests per authenticated session.
Monitoring Recommendations
- Enable verbose request logging on the Dockhand API, including user identity, source IP, and submitted template parameters.
- Forward Dockhand host network flow data and application logs to a central analytics platform for retention and query.
- Monitor cloud provider logs for metadata endpoint access and anomalous use of instance role credentials.
How to Mitigate CVE-2026-110255
Immediate Actions Required
- Upgrade Dockhand to version 1.0.43 or later on all hosts running the API.
- Rotate IAM credentials, instance role tokens, and any secrets reachable from the Dockhand host that may have been exposed.
- Restrict Dockhand API access to trusted operators and require strong authentication for template submission.
Patch Information
Finsys addressed CVE-2026-110255 in Dockhand 1.0.43. Review the GitHub Security Advisory GHSA-f2mx-74xq-g4p9 for fix details and upgrade guidance. The VulnCheck SSRF Advisory for Dockhand provides additional vulnerability context.
Workarounds
- Place Dockhand behind an egress proxy that blocks requests to 169.254.169.254, loopback, and RFC1918 destinations.
- Enforce IMDSv2 and require session tokens on AWS workloads to reduce the value of metadata responses retrieved through SSRF.
- Limit template submission permissions to a small set of trusted accounts until the upgrade is deployed.
# Example egress restriction using iptables on the Dockhand host
iptables -A OUTPUT -d 169.254.169.254 -j REJECT
iptables -A OUTPUT -d 127.0.0.0/8 -j REJECT
iptables -A OUTPUT -d 10.0.0.0/8 -j REJECT
iptables -A OUTPUT -d 172.16.0.0/12 -j REJECT
iptables -A OUTPUT -d 192.168.0.0/16 -j REJECT
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

