RHSA-2026:6478HighCVSS 8.1

Red Hat Security Advisory: Red Hat build of Keycloak 26.4.11 Images Update

Published
April 2, 2026
Last Modified
August 4, 2026

🔗 CVE IDs covered (15)

CVE-2025-14777 →CVE-2026-1035 →CVE-2026-3121 →CVE-2026-4282 →CVE-2026-4634 →CVE-2025-14082 →CVE-2025-14083 →CVE-2026-1180 →CVE-2026-2366 →CVE-2026-3429 →CVE-2026-3872 →CVE-2026-4636 →CVE-2026-3911 →CVE-2026-3190 →CVE-2026-4325 →

📋 Description

CVE-2025-14082 — keycloak-services: Keycloak Admin REST API: Improper Access Control leads to sensitive role metadata information disclosure CVE-2025-14083 — keycloak-server: Keycloak: Improper Access Control in Admin REST API leads to information disclosure CVE-2025-14777 — keycloak: Keycloak IDOR in realm client creating/deleting CVE-2026-1035 — org.keycloak.protocol.oidc: Keycloak Refresh Token Reuse Bypass via TOCTOU Race Condition CVE-2026-1180 — org.keycloak.protocol.oidc: Blind Server-Side Request Forgery (SSRF) in Keycloak OIDC Dynamic Client Registration via jwks_uri CVE-2026-2366 — keycloak: Keycloak: Information disclosure via authorization bypass in Admin API CVE-2026-3121 — keycloak: org.keycloak/keycloak-services: Keycloak: Privilege escalation via manage-clients permission CVE-2026-3190 — keycloak: Keycloak: Information Disclosure via improper role enforcement in UMA 2.0 Protection API CVE-2026-3429 — org.keycloak.services.resources.account: Improper Access Control Leading to MFA Deletion and Account Takeover in Keycloak Account REST API CVE-2026-3872 — keycloak: Keycloak: Information disclosure due to redirect_uri validation bypass CVE-2026-3911 — org.keycloak.services.resources.admin.UserResource: Keycloak: Information disclosure of disabled user attributes via administrative endpoint CVE-2026-4282 — keycloak: Keycloak: Privilege escalation via forged authorization codes due to SingleUseObjectProvider isolation flaw CVE-2026-4325 — keycloak: Keycloak: Replay of action tokens via improper handling of single-use entries CVE-2026-4634 — keycloak: Keycloak: Denial of Service via excessive processing of OpenID Connect scope parameters CVE-2026-4636 — keycloak: Keycloak: UMA policy bypass allows authenticated users to gain unauthorized access to victim-owned resources.

🎯 Affected products10

  • Red Hat build of Keycloak 26.4
  • rhbk/keycloak-operator-bundle@sha256:7fb041b0e2b43954c3a83b58fd885b1cdc5bb32275e06c4c72955da5b78255c3_amd64 as a component of Red Hat build of Keycloak 26.4
  • rhbk/keycloak-rhel9-operator@sha256:0d90a1c28652b5f73ea90f78968548178cf710121fcb13774a467aeb9c30ab09_s390x as a component of Red Hat build of Keycloak 26.4
  • rhbk/keycloak-rhel9-operator@sha256:1a7ac3c798d83cc37dd750ed44223630f4ebff937534a59a9e9ad029dbf31a0f_amd64 as a component of Red Hat build of Keycloak 26.4
  • rhbk/keycloak-rhel9-operator@sha256:715a5c6cc9061fc0305370a33f5b69a96ba7bfdb23b706a567b489fc05b05e06_ppc64le as a component of Red Hat build of Keycloak 26.4
  • rhbk/keycloak-rhel9-operator@sha256:c68d195c2d19568d9789648ef347a3388da453c83120d696453333c34a564347_arm64 as a component of Red Hat build of Keycloak 26.4
  • rhbk/keycloak-rhel9@sha256:33fc8c6edb3c5c2df302ea53a89454320e08ff4660ba84d0a78f6c67178dfb16_s390x as a component of Red Hat build of Keycloak 26.4
  • rhbk/keycloak-rhel9@sha256:a4cb583985eb220ad05b1983a98a5a50e2b76c15e6f56152045591e3994f37d1_ppc64le as a component of Red Hat build of Keycloak 26.4
  • rhbk/keycloak-rhel9@sha256:c1c1cb36f70ca142a789b359f9a120d321f58adc44e2c97a49c2d6f270d15bd9_arm64 as a component of Red Hat build of Keycloak 26.4
  • rhbk/keycloak-rhel9@sha256:dc54248ad9357fbd737e6983e6d8d0c7e845e39ed6558bd7c39f7a7573459489_amd64 as a component of Red Hat build of Keycloak 26.4

✅ Remediation

Before applying the update, back up your existing installation, including all applications, configuration files, databases and database settings, and so on. Workaround: Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: To mitigate this issue, configure the `refreshTokenMaxReuse` policy in Keycloak to a value greater than zero. This prevents the race condition by allowing a limited number of reuses for refresh tokens, thereby maintaining the integrity of the Refresh Token Rotation hardening measure. Consult Keycloak documentation for specific configuration instructions. Changes to Keycloak configuration typically require a service restart or redeployment to take effect. Workaround: To mitigate this vulnerability, avoid using wildcards in `redirect_uri` configurations within Keycloak. Restricting `redirect_uri` to explicit, fully qualified URIs prevents the bypass of validation logic. This configuration change may require a service restart or reload to take effect.

🔗 References (3)