# CVE-2026-94213: Keycloak-services: keycloak-services: authorization services policy evaluation endpoint leaks user identity

> Delegated administrators can access full user profiles and roles via the policy evaluation endpoint due to missing authorization checks.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-7238-mjjf-8jj4

## What is CVE-2026-94213?

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

### Official description

A flaw was found in the Authorization Services component of Keycloak, an open-source identity and access management solution. The issue occurs in the policy evaluation endpoint, which is used by administrators to test how access policies apply to specific users. Due to missing authorization checks, a delegated administrator with limited viewing privileges can access the full profile and role information of any user in the realm, even if they are not permitted to view user details. This could lead to the exposure of sensitive information such as email addresses and assigned security roles.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-94213 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94213 is a medium-severity missing authorization vulnerability in Red Hat Build of Keycloak, published on 21 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-94213 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-94213/ (Markdown: https://insights.sbomify.com/CVE-2026-94213/index.md)
```

## Sources

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

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