Skip to main content
Menu
CVEs

Dockhand cross-site request forgery in origin validation

Affects Dockhand before 1.0.57, where a logged-in user visiting a same-site attacker page can have forged POST requests sent to Dockhand. Fixed in 1.0.57.

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

6.1MediumCNA
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 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.

Who should check

Teams running Dockhand before 1.0.57 with logged-in users; the attack needs a same-site attacker page to lure those users.

“Affecting dockhand < 1.0.57”

vulncheck.com

What to do

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

    Victim must be authenticated with an active session and visit the attacker's page. The attacker page must be same-site with the Dockhand instance.
  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-134449 (Dockhand before 1.0.57 Cross-Site Request Forgery via Missing Origin Validation), 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-134449 (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):
- Victim must be authenticated with an active session and visit the attacker's page. (source: https://github.com/Finsys/dockhand/security/advisories/GHSA-c7r9-g9c5-xc8f)
- The attacker page must be same-site with the Dockhand instance. (source: https://www.vulncheck.com/advisories/dockhand-before-1.0.57-cross-site-request-forgery-via-missing-origin-validation)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-134449 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134449 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-c7r9-g9c5-xc8f
- https://www.vulncheck.com/advisories/dockhand-before-1.0.57-cross-site-request-forgery-via-missing-origin-validation
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-134449
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-134449"}.

Affected versions

cve.now Index

18Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.1/10CVSS 6.1
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active

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-c7r9-g9c5-xc8f
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134449
RecordNVD · CVE-2026-134449
Other links 1
Linkvulncheck.com · advisories/dockhand-before-1.0.57-cross-site-request-forgery-via-missing-origin-validation

Questions about CVE-2026-134449

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

Dockhand does not check where a request comes from, so a page on the same site as the Dockhand instance can send forged POST requests as a logged-in user. Those requests can stop, start, or delete stacks, change settings, and change credentials.

Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-134449?

dockhand: before 1.0.57.

Source: cve.now feed data

Am I affected, and how do I check?

Versions of Dockhand before 1.0.57 are affected. The attack needs a victim with an active session who visits the attacker's same-site page, so check the Dockhand version you run against 1.0.57.

Source: github.com, vulncheck.com

How do I fix CVE-2026-134449?

Upgrade Dockhand to version 1.0.57 or later, which is the listed fix for this vulnerability.

Source: github.com, vulncheck.com

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