# CVE-2026-19608: Keycloak-services: keycloak-services: name-only group claims let same-name groups satisfy path-specific group policies

> Attackers can gain unauthorized access to protected resources by exploiting group name collisions in Keycloak's authorization policies.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/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:** No
- **Published:** 18 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-qxf7-g44v-fgwh

## What is CVE-2026-19608?

CVE-2026-19608 is a medium-severity missing authorization vulnerability in Red Hat Build of Keycloak, published on 18 Aug 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 policy provider of Keycloak authorization services, which is used to manage fine-grained access control to resources. The issue occurs when the system evaluates group-based policies using tokens that only contain group names rather than full paths. If two groups in different parts of the organization share the same name, a user in the unauthorized group can be mistaken for a member of the authorized group. This can allow a user to gain unauthorized access to protected resources they should not be able to reach.

Weakness: CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-19608 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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