Red Hat build of Keycloak 26.4 vulnerabilities
52 known vulnerabilities in Red Hat build of Keycloak 26.4 from Red Hat. 52 are rated high or critical. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 7.5 High severity
Red Hat build of Keycloak 26.2: Improper Validation of Syntactic Correctness of Input
A flaw was found in Keycloak. A remote, unauthenticated attacker can send a specially crafted XML input to the Security Assertion Markup Language (SAML) endpoint. This malicious input can cause high CPU usage and worker thread starvation, leading to a Denial o
- 8.1 High severity
Red Hat build of Keycloak 26.2: Incorrect Behavior Order: Authorization Before Parsing and Canonicalization
A flaw was found in Keycloak. An authenticated user with the uma_protection role can bypass User-Managed Access (UMA) policy validation. This allows the attacker to include resource identifiers owned by other users in a policy creation request, even if the URL
- 7.5 High severity
Red Hat build of Keycloak 26.2: Excessive Platform Resource Consumption within a Loop
A flaw was found in Keycloak. An unauthenticated attacker can exploit this vulnerability by sending a specially crafted POST request with an excessively long scope parameter to the OpenID Connect (OIDC) token endpoint. This leads to high resource consumption a
- 7.4 High severity
Red Hat build of Keycloak 26.2: Improper Isolation or Compartmentalization
A flaw was found in Keycloak. The SingleUseObjectProvider, a global key-value store, lacks proper type and namespace isolation. This vulnerability allows an unauthenticated attacker to forge authorization codes. Successful exploitation can lead to the creation
- 7.3 High severity
Red Hat build of Keycloak 26.2: URL Redirection to Untrusted Site
A flaw was found in Keycloak. This issue allows an attacker, who controls another path on the same web server, to bypass the allowed path in redirect Uniform Resource Identifiers (URIs) that use a wildcard. A successful attack may lead to the theft of an acces
- 7.2 High severity
Red Hat build of Keycloak 26.4: Incorrect Privilege Assignment
A flaw was found in Keycloak. An administrator with `manage-clients` permission can exploit a misconfiguration where this permission is equivalent to `manage-permissions`. This allows the administrator to escalate privileges and gain control over roles, users,
- 8.1 High severity
Red Hat build of Keycloak 26.2: Missing Authentication for Critical Functionality
A flaw was found in Keycloak. A remote attacker could bypass security controls by sending a valid SAML response from an external Identity Provider (IdP) to the Keycloak SAML endpoint for IdP-initiated broker logins. This allows the attacker to complete broker
- 7.7 High severity
Red Hat build of Keycloak 26.2: Improper Validation of Specified Type of Input
A flaw was found in Keycloak. Keycloak's Security Assertion Markup Language (SAML) broker endpoint does not properly validate encrypted assertions when the overall SAML response is not signed. An attacker with a valid signed SAML assertion can exploit this by
- 8.8 High severity
Red Hat build of Keycloak 26.2: Authentication Bypass by Primary Weakness
A flaw was found in org.keycloak.broker.saml. When a disabled Security Assertion Markup Language (SAML) client is configured as an Identity Provider (IdP)-initiated broker landing target, it can still complete the login process and establish a Single Sign-On (
- 8.1 High severity
Red Hat build of Keycloak 26.4: Incorrect Authorization
A security flaw in the IdentityBrokerService.performLogin endpoint of Keycloak allows authentication to proceed using an Identity Provider (IdP) even after it has been disabled by an administrator. An attacker who knows the IdP alias can reuse a previously gen
- 8.1 High severity
Red Hat build of Keycloak 26.2: Improper Verification of Cryptographic Signature
A flaw was found in Keycloak. An attacker can exploit this vulnerability by modifying the organization ID and target email within a legitimate invitation token's JSON Web Token (JWT) payload. This lack of cryptographic signature verification allows the attacke
- 8.8 High severity
Red Hat build of Keycloak 26.4: Improperly Implemented Security Check for Standard
A flaw was found in Keycloak. A vulnerability exists in the jwt-authorization-grant flow where the server fails to verify if an Identity Provider (IdP) is enabled before issuing tokens. The issuer lookup mechanism (lookupIdentityProviderFromIssuer) retrieves t