# CVE-2026-15945: Keycloak-services: keycloak-services: group hierarchy search discloses hidden parent groups under fgap v2

> Delegated administrators can view unauthorized parent group details via search when Fine-Grained Admin Permissions v2 is enabled.

- **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:** Yes
- **Published:** 16 Jul 2026
- **Updated:** 16 Sep 2026
- **Also known as:** BIT-keycloak-2026-15945, GHSA-hp9p-wj8m-c339

## What is CVE-2026-15945?

CVE-2026-15945 is a medium-severity vulnerability in Redhat Build of Keycloak, published on 16 Jul 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 group search functionality of the Keycloak server's administrative API. When Fine-Grained Admin Permissions (FGAP) v2 is enabled, a delegated administrator can bypass access restrictions to view parent groups they are not authorized to see. By searching for a child group they have permission to view, the system incorrectly returns the full details of the parent group in the response, leading to the disclosure of sensitive group attributes and configuration.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

1 open source package ship an affected version, including keycloak. It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `keycloak` | Bitnami | All versions | 26.7.2 |

Products: Redhat Build of Keycloak, Redhat Data Grid, Redhat Jboss Enterprise Application Platform Expansion Pack, Redhat Single Sign-On.

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

Upgrade keycloak to 26.7.2 or later.

## Is CVE-2026-15945 being exploited?

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

## Other vulnerabilities in Redhat Build of Keycloak

- [CVE-2026-15572](https://insights.sbomify.com/CVE-2026-15572/): Keycloak-services: keycloak-services: dcr protocol mapper type-swap policy bypass allows privilege escalation (high 8.8)
- [CVE-2026-3047](https://insights.sbomify.com/CVE-2026-3047/): Keycloak SAML Broken has Authentication Bypass by Primary Weakness (high 8.8)
- [CVE-2026-15573](https://insights.sbomify.com/CVE-2026-15573/): Keycloak-services: keycloak-services: authorization bypass via unnormalized uri matching in pathmatcher (high 8.1)
- [CVE-2026-16102](https://insights.sbomify.com/CVE-2026-16102/): Keycloak-services: keycloak-services: default dcr policy allows role forgery via user property mappers (high 8.1)
- [CVE-2026-1609](https://insights.sbomify.com/CVE-2026-1609/): Org.keycloak/keycloak-quarkus-server: keycloak: unauthorized access via jwt authorization grant with disabled users (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15945 is a medium-severity vulnerability in Redhat Build of Keycloak, published on 16 Jul 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-15945 in the wild and no public exploit code.

Affected packages and fixed versions:
- keycloak (Bitnami): affected all versions; fixed in 26.7.2

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

## Sources

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

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