Keycloak: a bare group name in oidcAllowedGroups / adminGroups matches a group of that name at any depth #988

Closed
opened 2026-10-24 16:13:00 +00:00 by Cordy · 2 comments
Owner

Found in the #985 research (research-985-4 §4.2).

oidcAllowedRecheck (recheck.go:155) accepts set[r.Name], so a bare entry cairn-users matches /cairn-users, /partner/cairn-users and any other group named cairn-users anywhere in the realm. Whoever can create a subgroup somewhere can grant access. Keycloak treated exactly this matching as a vulnerability and fixed it (CVE-2026-19608; Keycloak 26.8 reads a bare name as a top-level group). VERIFIED (code, advisory).

At sign-in Cairn compares the claim exactly (oidc.go:114): with "Full group path" on (default) a bare entry never matches at sign-in; with it off, any group of that name matches at sign-in too. So sign-in and re-check can disagree.

Options.

  1. Follow Keycloak 26.8: a bare entry means a top-level group (sign-in and re-check alike).
  2. Minimum: WARN at start and in the Users & access facts block when a bare entry matches more than one group ("ambiguous: list the full path").

Applies to oidcAllowedGroups and adminGroups. Needs a decision before the fix (asked in #985).

Found in the #985 research (research-985-4 §4.2). `oidcAllowedRecheck` (`recheck.go:155`) accepts `set[r.Name]`, so a bare entry `cairn-users` matches `/cairn-users`, `/partner/cairn-users` and any other group named `cairn-users` anywhere in the realm. Whoever can create a subgroup somewhere can grant access. Keycloak treated exactly this matching as a vulnerability and fixed it (CVE-2026-19608; Keycloak 26.8 reads a bare name as a top-level group). VERIFIED (code, advisory). At sign-in Cairn compares the claim exactly (`oidc.go:114`): with "Full group path" on (default) a bare entry never matches at sign-in; with it off, any group of that name matches at sign-in too. So sign-in and re-check can disagree. **Options.** 1. Follow Keycloak 26.8: a bare entry means a top-level group (sign-in and re-check alike). 2. Minimum: WARN at start and in the Users & access facts block when a bare entry matches more than one group ("ambiguous: list the full path"). Applies to `oidcAllowedGroups` and `adminGroups`. Needs a decision before the fix (asked in #985).
Author
Owner

Decision (Nikola, 2026-10-24): top-level only. A bare entry in oidcAllowedGroups / adminGroups means a top-level group, identically at sign-in and at re-check (Keycloak 26.8 rule for CVE-2026-19608). Subgroups need the full path. Start-up WARN when a bare entry exists only as a subgroup; upgrade note in the CHANGELOG. Lands with the #985 batch.

Decision (Nikola, 2026-10-24): **top-level only**. A bare entry in `oidcAllowedGroups` / `adminGroups` means a top-level group, identically at sign-in and at re-check (Keycloak 26.8 rule for CVE-2026-19608). Subgroups need the full path. Start-up WARN when a bare entry exists only as a subgroup; upgrade note in the CHANGELOG. Lands with the #985 batch.
Author
Owner

Fixed in v0.6.354 (PR #1004). A bare entry means a top-level group in oidcAllowedGroups, adminGroups (path-compared at sign-in, at re-check and in live group refresh), space operations and peering receiver groups. The start check WARNs when a bare entry exists only as a subgroup and retries until it succeeds; the result is shown in Users & access. The upgrade notes say:

  • Keycloak's "Full group path" must be on.
  • Case must match the realm.

Not yet covered: access to directory-group spaces and group shares, followed up in #1002. Closing.

Fixed in v0.6.354 (PR #1004). A bare entry means a top-level group in `oidcAllowedGroups`, `adminGroups` (path-compared at sign-in, at re-check and in live group refresh), space operations and peering receiver groups. The start check WARNs when a bare entry exists only as a subgroup and retries until it succeeds; the result is shown in Users & access. The upgrade notes say: - Keycloak's "Full group path" must be on. - Case must match the realm. Not yet covered: access to directory-group spaces and group shares, followed up in #1002. Closing.
Cordy closed this issue 2026-10-25 21:29:30 +00:00
Sign in to join this conversation.
No labels
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#988
No description provided.