# CVE-2026-94000: Privilege escalation in Red Hat Build of Keycloak

> A delegated administrator can escalate to realm-admin by adding themselves to a high-privilege group due to missing permission checks in the Admin REST API.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-3g7j-6fqv-v2q4

## What is CVE-2026-94000?

CVE-2026-94000 is a medium-severity vulnerability in Red Hat Build of Keycloak, published on 19 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A flaw was found in the Admin REST API of Keycloak, an open-source identity and access management solution. The issue occurs in the group-membership endpoints where the system fails to check if a group grants administrative privileges before allowing a user to be added. This allows a delegated administrator with limited permissions to add themselves to a high-privilege group, potentially gaining full control over the entire realm.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-94000 being exploited?

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

Public exploit code:

- Reproducible Docker lab + PoC: Keycloak manage-users -> realm-admin escalation via composite roles (CVE-2026-94000 variant). Validated on 26.8.1. (github_poc): https://github.com/SecFathy/KeycloakESC

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94000 is a medium-severity vulnerability in Red Hat Build of Keycloak, published on 19 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-94000 in the wild and no public exploit code.

Affected product: Red Hat Build of Keycloak. 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-94000/ (Markdown: https://insights.sbomify.com/CVE-2026-94000/index.md)
```

## Sources

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

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