# CVE-2026-14613: Information disclosure in Red Hat Build of Keycloak

> Restricted administrators can view hidden group metadata when Fine-Grained Admin Permissions are enabled, exposing sensitive internal details.

- **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:** 3 Jul 2026
- **Updated:** 31 Aug 2026
- **Also known as:** BIT-keycloak-2026-14613, GHSA-j2vp-w8g9-p6hf, UBUNTU-CVE-2026-14613

## What is CVE-2026-14613?

CVE-2026-14613 is a medium-severity vulnerability in Redhat Build of Keycloak, published on 3 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was discovered in Keycloak's administrative interface that allows certain administrators to see information about groups they shouldn't have access to. When the new Fine-Grained Admin Permissions (FGAP v2) are turned on, an administrator who is allowed to see a specific "role" can also see a list of all groups assigned to that role. The system fails to check if the administrator has permission to see those specific groups. This could allow a restricted administrator to discover "hidden" groups and see their details, such as internal names and custom settings, which might contain sensitive deployment information.

Weakness: CWE-284 (Improper Access Control), CWE-1220 (Insufficient Granularity of Access Control)

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

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.2 |

Products: Redhat Build of Keycloak.

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

Upgrade keycloak to 26.7.2 or later.

## Is CVE-2026-14613 being exploited?

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

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

## Sources

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

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