# CVE-2026-92894: Rubygem-foreman_ansible: unscoped lookupvalue deletion allows cross-model override value destruction

> Authenticated users can delete arbitrary lookup values, destroying configuration data for Ansible and Puppet variables outside their authorized scope.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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-xw4h-j68j-jhc2

## What is CVE-2026-92894?

CVE-2026-92894 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 override values API. The destroy action resolves the target LookupValue record by ID without verifying it belongs to an AnsibleVariable the caller is authorized to edit. An authenticated user with the edit_ansible_variables permission can delete any LookupValue by ID, including override values for Ansible variables outside their permission filter scope and override values belonging to Puppet smart class parameters.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-92894 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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