# CVE-2026-105834: Rundeck before 6.2.0 Arbitrary File Read via File Resource Model Source

> Attackers with project configure permissions can read arbitrary server files, exposing sensitive credentials and data.

- **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
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-3xjf-2x46-6jp7

## What is CVE-2026-105834?

CVE-2026-105834 is a high-severity path traversal vulnerability in rundeck, published on 6 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Rundeck before 6.2.0 contains a path traversal vulnerability that allows users holding only the project configure ACL to read arbitrary server files by setting resources.source.N.config.file to any absolute path. Attackers can retrieve file contents through editProjectNodeSourceFile or the apiSourceGetContent endpoint to obtain database passwords, LDAP bind credentials, and other projects' data.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-105834 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105834 is a high-severity path traversal vulnerability in rundeck, published on 6 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105834 in the wild and no public exploit code.

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

## Sources

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

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