# CVE-2026-110112: Dockhand before 1.0.50 OIDC Privilege Escalation via Missing Token Claim Validation

> Attackers from other tenants can gain admin access in Dockhand due to missing OIDC token claim validation, allowing unauthorized privilege escalation.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 17 Oct 2026
- **Also known as:** GHSA-2v42-28fc-4w3q, GHSA-h4vc-h76x-c279

## What is CVE-2026-110112?

CVE-2026-110112 is a critical vulnerability in Finsys dockhand, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dockhand before 1.0.50 contains a privilege escalation vulnerability that allows users from another tenant to gain admin access because OIDC iss, aud, nonce and exp claims are not validated. Attackers with admin rights in another tenant of a shared provider like Microsoft Entra ID can recreate the mapped admin group and log in as Dockhand administrators.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-110112?


## How do I fix CVE-2026-110112?

No fix has been published for CVE-2026-110112 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-110112 being exploited?

There is no known exploitation of CVE-2026-110112 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-110112 and fix it if it is affected.

What it is: CVE-2026-110112 is a critical vulnerability in Finsys dockhand, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-110112 in the wild and no public exploit code.

Affected product: Finsys dockhand. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-110112/ (Markdown: https://insights.sbomify.com/CVE-2026-110112/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-110112
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-110112
- OSV: https://osv.dev/vulnerability/CVE-2026-110112

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-110112/
Summaries are generated and may contain mistakes; the official description above is the record.