# CVE-2026-92893: Rubygem-foreman_ansible: ansible inventory api ignores view_hosts permission filters, exposes hidden parameters

> Authenticated users can bypass host visibility filters to access hidden Ansible inventory parameters for arbitrary hosts.

- **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-pvvq-573r-296r

## What is CVE-2026-92893?

CVE-2026-92893 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_ansible plugin's Ansible inventory API. The controller builds its host query using an unscoped Host.where call that does not enforce the search filter associated with the caller's view_hosts permission. An authenticated user whose host visibility is restricted by a permission filter can supply arbitrary host IDs within their organization and receive the full Ansible inventory for those hosts, including parameter values marked as hidden.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-92893 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92893 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-92893 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-92893/ (Markdown: https://insights.sbomify.com/CVE-2026-92893/index.md)
```

## Sources

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

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