Skip to main content
Menu
CVEs

Dockhand access control bypass in API endpoints

Dockhand 1.0.49 and older has API endpoints that skip RBAC permission checks, so low-privileged users can read data they should not see. Fixed in 1.0.50.

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

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 1.0.50
Who is exposed
Specific setups only

Summary

Written by a model

Dockhand before 1.0.50 contains an improper access control vulnerability that allows authenticated unprivileged users to read restricted data by querying API endpoints lacking RBAC checks. Attackers can access /api/users, /api/license, and /api/hawser/connect to obtain user emails and roles, the full license key, and environment details, while an invalid license grants all users admin rights.

Who should check

Teams running Dockhand 1.0.49 or older as a Docker management UI, especially instances with multiple user accounts and RBAC roles.

“In Dockhand 1.0.49 and older”

github.com

What to do

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

    Dockhand version 1.0.49 and older An expired, corrupted or hostname-mismatched enterprise license (in 1.0.49 and older) makes every user a full administrator
  2. Upgrade to a fixed version: 1.0.50.

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-134453 (Dockhand before 1.0.50 Improper RBAC Enforcement via API Endpoints), 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-134453 (entry last updated 2026-11-21):
Affected:
- Finsys dockhand: fixed in 1.0.50
Fixed versions: 1.0.50.
Conditions (all must be true for the bug to be hit):
- Dockhand version 1.0.49 and older (source: https://github.com/Finsys/dockhand/security/advisories/GHSA-jv86-6qpr-739g)
- An expired, corrupted or hostname-mismatched enterprise license (in 1.0.49 and older) makes every user a full administrator (source: https://github.com/Finsys/dockhand/security/advisories/GHSA-jv86-6qpr-739g)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134453 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134453 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-jv86-6qpr-739g
- https://www.vulncheck.com/advisories/dockhand-before-1.0.50-improper-rbac-enforcement-via-api-endpoints
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-134453
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-134453"}.

Affected versions

cve.now Index

15Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 22 if CISA's SSVC rates it automatable

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-jv86-6qpr-739g
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134453
RecordNVD · CVE-2026-134453
Other links 1
Linkvulncheck.com · advisories/dockhand-before-1.0.50-improper-rbac-enforcement-via-api-endpoints

Questions about CVE-2026-134453

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

Several Dockhand API endpoints did not correctly check role-based access permissions, so low-privileged users could read the list of all users with names, emails and roles, the instance license key, settings, and Hawser environment details. In 1.0.49 and older, an expired, corrupted or hostname-mismatched enterprise license also made every user a full administrator.

Source: github.com

Which versions are affected by CVE-2026-134453?

dockhand: before 1.0.50.

Source: cve.now feed data

Am I affected, and how do I check?

Dockhand 1.0.49 and older is affected. The license-related escalation applies to installations with an enterprise license that is expired, corrupted or hostname-mismatched. Compare the installed Dockhand version with 1.0.50 to see whether it falls in the affected range.

Source: github.com

How do I fix CVE-2026-134453?

Upgrade Dockhand to version 1.0.50 or later, which is the fixed version listed for this vulnerability.

Source: github.com

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