# CVE-2026-112305: Semaphore UI through 2.19.16 RCE via Task Environment Ansible Variable Override

> Users with task_runner role can execute arbitrary commands as the server user by overriding protected Ansible variables in task environments.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/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:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-6cr7-7xqc-c37c

## What is CVE-2026-112305?

CVE-2026-112305 is a high-severity code injection vulnerability in semaphoreui Semaphore UI, published on 19 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Semaphore UI through 2.19.16 contains a remote code execution vulnerability that allows users with the task_runner role to override protected Ansible variables by supplying arbitrary keys in the task environment JSON. Attackers can POST tasks setting ansible_ssh_common_args with a ProxyCommand or ansible_connection=local to execute commands as the Semaphore server user, exposing encryption keys, SSH keys and stored secrets.

Weakness: CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes)

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


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

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

## Is CVE-2026-112305 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112305 is a high-severity code injection vulnerability in semaphoreui Semaphore UI, published on 19 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-112305 in the wild and no public exploit code.

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

## Sources

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

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