Red Hat Build Of Keycloak
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Red Hat Build Of Keycloak.
Recent Red Hat Build Of Keycloak Security Advisories
| Advisory | Title | Published |
|---|---|---|
| RHSA-2025:8690 | (RHSA-2025:8690) Important: Red Hat build of Keycloak 26.2.5 Security Update | June 9, 2025 |
| RHSA-2025:8672 | (RHSA-2025:8672) Important: Red Hat build of Keycloak 26.2.5 Images Security Update | June 9, 2025 |
| RHSA-2025:4336 | (RHSA-2025:4336) Important: Red Hat build of Keycloak 26.0.11 Update | April 29, 2025 |
| RHSA-2025:4335 | (RHSA-2025:4335) Important: Red Hat build of Keycloak 26.0.11 Images Update | April 29, 2025 |
| RHSA-2025:2545 | (RHSA-2025:2545) Moderate: Red Hat build of Keycloak 26.0.10 Update | March 10, 2025 |
| RHSA-2025:2544 | (RHSA-2025:2544) Moderate: Red Hat build of Keycloak 26.0.10 Images Update | March 10, 2025 |
| RHSA-2025:0300 | (RHSA-2025:0300) Moderate: Red Hat build of Keycloak 26.0.8 Update | January 13, 2025 |
| RHSA-2025:0299 | (RHSA-2025:0299) Moderate: Red Hat build of Keycloak 26.0.8 Images Update | January 13, 2025 |
| RHSA-2024:10178 | (RHSA-2024:10178) Important: Red Hat build of Keycloak 26.0.6 Update | November 21, 2024 |
| RHSA-2024:10177 | (RHSA-2024:10177) Important: Red Hat build of Keycloak 26.0.6 Images Update | November 21, 2024 |
By the Year
In 2025 there have been 0 vulnerabilities in Red Hat Build Of Keycloak. Last year, in 2024 Build Of Keycloak had 7 security vulnerabilities published. Right now, Build Of Keycloak is on track to have less security vulnerabilities in 2025 than it did last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2025 | 0 | 0.00 |
| 2024 | 7 | 6.49 |
| 2023 | 0 | 0.00 |
| 2022 | 0 | 0.00 |
| 2021 | 0 | 0.00 |
| 2020 | 0 | 0.00 |
| 2019 | 0 | 0.00 |
| 2018 | 0 | 0.00 |
It may take a day or so for new Build Of Keycloak vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Red Hat Build Of Keycloak Security Vulnerabilities
A vulnerability was found in Wildfly, where a user may perform Cross-site scripting in the Wildfly deployment system
CVE-2024-10234
7.3 - High
- October 22, 2024
A vulnerability was found in Wildfly, where a user may perform Cross-site scripting in the Wildfly deployment system. This flaw allows an attacker or insider to execute a deployment with a malicious payload, which could trigger undesired behavior against the server.
XSS
A misconfiguration flaw was found in Keycloak
CVE-2024-8883
6.1 - Medium
- September 19, 2024
A misconfiguration flaw was found in Keycloak. This issue can allow an attacker to redirect users to an arbitrary URL if a 'Valid Redirect URI' is set to http://localhost or http://127.0.0.1, enabling sensitive information such as authorization codes to be exposed to the attacker, potentially leading to session hijacking.
Open Redirect
A session fixation issue was discovered in the SAML adapters provided by Keycloak
CVE-2024-7341
7.1 - High
- September 09, 2024
A session fixation issue was discovered in the SAML adapters provided by Keycloak. The session ID and JSESSIONID cookie are not changed at login time, even when the turnOffChangeSessionIdOnLogin option is configured. This flaw allows an attacker who hijacks the current session before authentication to trigger session fixation.
Session Fixation
A vulnerability was found in Keycloak
CVE-2024-7318
4.8 - Medium
- September 09, 2024
A vulnerability was found in Keycloak. Expired OTP codes are still usable when using FreeOTP when the OTP token period is set to 30 seconds (default). Instead of expiring and deemed unusable around 30 seconds in, the tokens are valid for an additional 30 seconds totaling 1 minute. A one time passcode that is valid longer than its expiration time increases the attack window for malicious actors to abuse the system and compromise accounts. Additionally, it increases the attack surface because at any given time, two OTPs are valid.
Use of a Key Past its Expiration Date
An open redirect vulnerability was found in Keycloak
CVE-2024-7260
6.1 - Medium
- September 09, 2024
An open redirect vulnerability was found in Keycloak. A specially crafted URL can be constructed where the referrer and referrer_uri parameters are made to trick a user to visit a malicious webpage. A trusted URL can trick users and automation into believing that the URL is safe, when, in fact, it redirects to a malicious server. This issue can result in a victim inadvertently trusting the destination of the redirect, potentially leading to a successful phishing attack or other types of attacks. Once a crafted URL is made, it can be sent to a Keycloak admin via email for example. This will trigger this vulnerability when the user visits the page and clicks the link. A malicious actor can use this to target users they know are Keycloak admins for further attacks. It may also be possible to bypass other domain-related security checks, such as supplying this as a OAuth redirect uri. The malicious actor can further obfuscate the redirect_uri using URL encoding, to hide the text of the actual malicious website domain.
Open Redirect
A vulnerability was found in Keycloak
CVE-2024-4629
6.5 - Medium
- September 03, 2024
A vulnerability was found in Keycloak. This flaw allows attackers to bypass brute force protection by exploiting the timing of login attempts. By initiating multiple login requests simultaneously, attackers can exceed the configured limits for failed attempts before the system locks them out. This timing loophole enables attackers to make more guesses at passwords than intended, potentially compromising account security on affected systems.
Improper Enforcement of a Single, Unique Action
A vulnerability was found in Undertow where the ProxyProtocolReadListener reuses the same StringBuilder instance across multiple requests
CVE-2024-7885
7.5 - High
- August 21, 2024
A vulnerability was found in Undertow where the ProxyProtocolReadListener reuses the same StringBuilder instance across multiple requests. This issue occurs when the parseProxyProtocolV1 method processes multiple requests on the same HTTP connection. As a result, different requests may share the same StringBuilder instance, potentially leading to information leakage between requests or responses. In some cases, a value from a previous request or response may be erroneously reused, which could lead to unintended data exposure. This issue primarily results in errors and connection termination but creates a risk of data leakage in multi-request environments.
Race Condition
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Oracle or by Red Hat? Click the Watch button to subscribe.
