# CVE-2026-1961: Forman: foreman: remote code execution via command injection in websocket proxy

> Remote attackers can execute arbitrary code on Foreman servers via command injection in the WebSocket proxy when accessing VNC consoles.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Mar 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-fh2w-2c26-vpg5

## What is CVE-2026-1961?

CVE-2026-1961 is a high-severity command injection vulnerability in Redhat Satellite, published on 26 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A flaw was found in Foreman. A remote attacker could exploit a command injection vulnerability in Foreman's WebSocket proxy implementation. This vulnerability arises from the system's use of unsanitized hostname values from compute resource providers when constructing shell commands. By operating a malicious compute resource server, an attacker could achieve remote code execution on the Foreman server when a user accesses VM VNC console functionality. This could lead to the compromise of sensitive credentials and the entire managed infrastructure.

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

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

It affects 2 products.


Products: Redhat Satellite, Theforeman Foreman.

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

Apply the vendor's patch.

## Is CVE-2026-1961 being exploited?

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

Public exploit code:

- PoC for CVE-2026-1961 — command injection in Foreman's WebSocket proxy (lib/ws_proxy.rb) via unsanitized compute resource hostname, leading to RCE as the foreman user. Responsibly disclosed and patched. (github_poc): https://github.com/kalnux/CVE-2026-1961-foreman-poc

## Other vulnerabilities in Redhat Satellite

- [CVE-2024-7012](https://insights.sbomify.com/CVE-2024-7012/): Puppet-foreman: an authentication bypass vulnerability exists in foreman (critical 9.8)
- [CVE-2024-7923](https://insights.sbomify.com/CVE-2024-7923/): Puppet-pulpcore: an authentication bypass vulnerability exists in pulpcore (critical 9.8)
- [CVE-2026-96659](https://insights.sbomify.com/CVE-2026-96659/): Foreman: excessive permissions for viewer role on preview (critical 9.1)
- [CVE-2023-0118](https://insights.sbomify.com/CVE-2023-0118/): Foreman: arbitrary code execution through templates (critical 9.1)
- [CVE-2008-2369](https://insights.sbomify.com/CVE-2008-2369/): Hardcoded credentials in n/a (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1961 is a high-severity command injection vulnerability in Redhat Satellite, published on 26 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1961 exists.

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

## Sources

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

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