Skip to main content
CVE-2026-134451VulnerabilityPublished

Dockhand before 1.0.57 contains a privilege escalation vulnerability that allows non-admin users with settings:edit

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-134451· High 8.6

Not known to be exploited · CVSS 8.6 High : upgrade to 1.0.57 soon.

Data as of 21 Nov 2026, 19:14 UTC

CVSS 4.0 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.6
CNA (VulnCheck)CVSS 3.18.1
Patch
Available – fixed in 1.0.57
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Upgrade dockhand and finsys/dockhand to 1.0.57.

Affected software

ProductAffectedFixed in
FinsysdockhandAffected
  • <1.0.57
Fixed in
  • 1.0.57
GitHubfinsys/dockhandpkg:github/finsys/dockhandOther threatsAffected
  • <1.0.57
Fixed in
  • 1.0.57

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Dockhand version 1.0.57 and later. Users should upgrade to version 1.0.57 or newer to remediate this vulnerability. No other mitigation or workaround is indicated.

Description

Dockhand versions prior to 1.0.57 have a privilege escalation vulnerability that allows non-admin users with the settings:edit permission to modify the OpenID Connect (OIDC) provider configuration. This occurs due to an improper permission check. Exploiting this flaw, an attacker can send a crafted PUT request to the OIDC provider endpoint to set the adminClaim to their own OIDC group, resulting in full administrative access upon their next OIDC login.

References

Community reviews

Loading reviews…