# CVE-2026-106056: Rundeck before 6.2.0 OS Command Injection via Windows Job Option Quoting

> Authenticated users can execute arbitrary OS commands on Windows nodes via crafted job options due to improper quoting.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/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:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-jv2x-5hph-7fp2

## What is CVE-2026-106056?

CVE-2026-106056 is a high-severity command injection vulnerability in rundeck, published on 7 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 an OS command injection vulnerability that allows authenticated users with job run permission to execute commands on Windows nodes by supplying crafted option values. Attackers can inject cmd.exe metacharacters such as && or | into free-text options, which CLIUtils.quoteWindowsCMDArg wraps in ineffective single quotes, running commands with node executor credential privileges.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-106056 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-106056 is a high-severity command injection vulnerability in rundeck, published on 7 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-106056 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-106056/ (Markdown: https://insights.sbomify.com/CVE-2026-106056/index.md)
```

## Sources

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

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