# CVE-2026-113354: Dockhand before 1.0.46 Arbitrary File Read via /api/system/files/content


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-433w-5hff-22h6, GHSA-j864-cxh9-gqc9

## What is CVE-2026-113354?

CVE-2026-113354 is a high-severity vulnerability in Finsys dockhand, published on 20 Oct 2026. 

### Official description

Dockhand before 1.0.46 contains an arbitrary file read vulnerability that allows non-admin users with stacks:edit permission to read files through the path parameter of /api/system/files/content. Attackers can supply absolute paths to read /etc/shadow, /etc/passwd, git .git/config credentials, and SSH keys from the Dockhand container.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-113354 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113354 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113354 is a high-severity vulnerability in Finsys dockhand, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113354 exists.

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-113354/ (Markdown: https://insights.sbomify.com/CVE-2026-113354/index.md)
```

## Sources

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

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