# CVE-2026-16105: Keycloak-services: keycloak-services: missing per-role authorization on rolecontainerresource composite endpoints

> A delegated administrator can remove essential child roles from built-in admin roles due to missing authorization checks, disrupting administrative functions.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Jul 2026
- **Updated:** 16 Sep 2026
- **Also known as:** BIT-keycloak-2026-16105, CLEANSTART-2026-HP97605, GHSA-w32v-46r7-99r7

## What is CVE-2026-16105?

CVE-2026-16105 is a medium-severity missing authorization vulnerability in Redhat Build of Keycloak, published on 31 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A flaw was found in the RoleContainerResource component of Keycloak. The issue occurs because certain name-based endpoints in the admin REST API do not properly enforce authorization checks when managing composite roles. This allows a delegated administrator with manage-realm permissions to remove essential child roles from built-in admin roles, potentially disrupting administrative functions within a realm.

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

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

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


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

Products: Redhat Build of Keycloak.

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

Upgrade keycloak to 26.7.3 or later.

## Is CVE-2026-16105 being exploited?

There is no known exploitation of CVE-2026-16105 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-16105 and fix it if it is affected.

What it is: CVE-2026-16105 is a medium-severity missing authorization vulnerability in Redhat Build of Keycloak, published on 31 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-16105 in the wild and no public exploit code.

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

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

## Sources

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

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