Skip to main content
Menu
CVEs

Dockhand clickjacking via missing frame protection headers

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

2.3LowCNA
Exploited
No known exploitation
Fix
Fixed in 1.0.57
Who is exposed
Specific setups only

Summary

Dockhand before 1.0.57 contains a clickjacking vulnerability because src/hooks.server.ts never sets X-Frame-Options or CSP frame-ancestors headers on responses. Attackers on a same-site origin can embed the UI in an invisible iframe to trick authenticated users into stopping stacks, deleting resources, or changing settings.

Who should check

Teams running the Dockhand web UI (npm package dockhand) before 1.0.57, especially admins who use it while logged in.

“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 1.0.56 and earlier). The attacker page is on a same-site origin. The victim has an active authenticated Dockhand session and visits the attacker's page.
  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-134450 (Dockhand before 1.0.57 Clickjacking via Missing Frame Protection Headers), 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-134450 (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 1.0.56 and earlier). (source: https://www.vulncheck.com/advisories/dockhand-before-1.0.57-clickjacking-via-missing-frame-protection-headers)
- The attacker page is on a same-site origin. (source: https://www.vulncheck.com/advisories/dockhand-before-1.0.57-clickjacking-via-missing-frame-protection-headers)
- The victim has an active authenticated Dockhand session and visits the attacker's page. (source: https://github.com/Finsys/dockhand/security/advisories/GHSA-c267-pq9x-m45w)
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-134450 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134450 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-c267-pq9x-m45w
- https://www.vulncheck.com/advisories/dockhand-before-1.0.57-clickjacking-via-missing-frame-protection-headers
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-134450
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-134450"}.

Affected versions

cve.now Index

14Pof 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
  • Severity2.3/10CVSS 2.3
  • No patch0/5No signal

What would change the score

  • Would score about 64 if added to CISA KEV
  • Would score about 59 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-c267-pq9x-m45w
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134450
RecordNVD · CVE-2026-134450
Other links 1
Linkvulncheck.com · advisories/dockhand-before-1.0.57-clickjacking-via-missing-frame-protection-headers

Questions about CVE-2026-134450

Is CVE-2026-134450 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's UI can be embedded in a frame on a page from a same-site origin, so an attacker can trick a logged-in user into clicking destructive controls. The impact includes stopping stacks, deleting services, or changing credentials, all without the user intending it.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134450?

dockhand: before 1.0.57.

Source: cve.now feed data

Am I affected, and how do I check?

Dockhand 1.0.56 and earlier are affected, with the condition that the attacker's page is on a same-site origin and the victim has an active authenticated Dockhand session while visiting that page. To check your version, look at the Dockhand version shown in the product.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134450?

Upgrade Dockhand to version 1.0.57, which is the fixed version listed for this vulnerability.

Source: vulncheck.com, github.com

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