CVE-2026-134449 in Dockhandinfo

Summary

by MITRE • 11/21/2026

Dockhand before 1.0.57 contains a cross-site request forgery vulnerability that allows attackers to perform state-changing actions by exploiting missing Origin header validation and absent CSRF tokens. Attackers can lure authenticated users to a same-site attacker page that submits forged POST requests to stop, start, or delete stacks, modify settings, and change credentials.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Analysis

by VulDB Data Team • 11/21/2026

The security flaw identified in Dockhand versions prior to 1.0.57 represents a critical failure in implementing robust cross-site request forgery defenses, specifically categorized under CWE-352 as Cross-Site Request Forgery. This vulnerability stems from the application's inability to properly validate the Origin header and its complete absence of anti-CSRF tokens within state-changing HTTP requests. In modern web security architectures, validating the Origin or Referer headers is a standard practice to ensure that incoming requests originate from trusted domains, while CSRF tokens provide an additional layer of verification by requiring unique, unpredictable values tied to the user's session. The lack of these mechanisms in Dockhand creates a significant attack surface where authenticated users can be manipulated into performing actions they did not intend to execute.

The operational impact of this vulnerability is severe due to the sensitive nature of the administrative functions exposed through the application interface. An attacker can craft a malicious webpage that, when visited by an authenticated user with active privileges in Dockhand, automatically submits forged POST requests to the vulnerable endpoints. These automated submissions allow the adversary to stop or start container stacks, which disrupts service availability and operational continuity for users relying on those resources. Furthermore, the ability to modify application settings can lead to configuration drift that compromises security postures or system stability. Most critically, the capability to change credentials allows an attacker to take over administrative accounts, potentially leading to full compromise of the Dockhand instance and any connected infrastructure managed through it.

This attack vector aligns with MITRE ATT&CK technique T1566.002, which describes Spearphishing Link attacks where users are lured to a malicious site that exploits browser trust relationships. Because the vulnerability relies on the user's existing authentication session, no additional credentials or social engineering beyond directing the victim to the attacker-controlled page are required. The exploitation is fully automated once the victim visits the malicious URL, making it highly efficient for attackers targeting environments where Dockhand is used as a management interface for container orchestration tasks.

To mitigate this vulnerability, immediate upgrade to version 1.0.57 or later is recommended, as these versions address the missing validation logic and implement proper CSRF protections. For organizations unable to patch immediately, implementing reverse proxy configurations that enforce strict Origin header checking can provide a temporary mitigation layer. Additionally, deploying Web Application Firewalls with rules designed to detect anomalous POST request patterns lacking expected security headers may help block exploitation attempts in real-time. Long-term remediation should involve adopting secure coding standards that mandate the inclusion of synchronized CSRF tokens for all state-changing operations and rigorous validation of source headers on every sensitive endpoint.

Responsible

VulnCheck

Reservation

11/21/2026

Disclosure

11/21/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Do you need the next level of professionalism?

Upgrade your account now!