# CVE-2026-92904: Rubygem-foreman_remote_execution: job output readable without object-level view_job_invocations check

> Authenticated users can read sensitive job output and script details from other users' invocations due to missing permission checks in the Foreman Remote Execution plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A: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:** 17 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-rx5v-pg4m-7r6r

## What is CVE-2026-92904?

CVE-2026-92904 is a medium-severity missing authorization vulnerability in Red Hat Satellite 6, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in the foreman_remote_execution plugin's template invocations controller. The show_template_invocation_by_host action resolves the job invocation by ID without evaluating the caller's view_job_invocations permission filter against the record. An authenticated user whose job invocation visibility is restricted by a permission filter can enumerate job invocation IDs and read the live output, rendered script, and input values for other users' job invocations within their own organizations.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-92904 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92904 is a medium-severity missing authorization vulnerability in Red Hat Satellite 6, published on 17 Sep 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-92904 in the wild and no public exploit code.

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

## Sources

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

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