Red Hat build of Keycloak 26.2 vulnerabilities
14 known vulnerabilities in Red Hat build of Keycloak 26.2 from Red Hat. 14 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: Authentication Bypass by Spoofing
A session fixation vulnerability was found in Keycloak's login-actions endpoints. An unauthenticated attacker could exploit this flaw by pre-creating an authentication session and tricking a victim into visiting a maliciously crafted link. By leveraging the /l
- 8.1 High severity
Red Hat build of Keycloak 26.2: URL Redirection to Untrusted Site
A flaw was found in Keycloak's URL validation logic during redirect operations. By crafting a malicious request, an attacker could bypass validation to redirect users to unauthorized URLs, potentially leading to the exposure of sensitive information within the
- 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
- 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.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
- 7.5 High severity
Red Hat build of Keycloak 26.0: Allocation of Resources Without Limits or Throttling
A flaw was found in Keycloak. This vulnerability allows an unauthenticated remote attacker to cause a denial of service (DoS) by repeatedly initiating TLS 1.2 client-initiated renegotiation requests to exhaust server CPU resources, making the service unavailab
- 7.1 High severity
Red Hat build of Keycloak 26: Origin Validation Error
A flaw was found in Keycloak. When an authenticated attacker attempts to merge accounts with another existing account during an identity provider (IdP) login, the attacker will subsequently be prompted to "review profile" information. This vulnerability allows
- 7.4 High severity
Cryostat 4 on RHEL 9: Inconsistent Interpretation of HTTP Requests
A flaw was found in Quarkus-HTTP, which incorrectly parses cookies with certain value-delimiting characters in incoming requests. This issue could allow an attacker to construct a cookie value to exfiltrate HttpOnly cookie values or spoof arbitrary additional