Build of Keycloak vulnerabilitiesRanked by how likely they are to be used.
Build of Keycloak is made by Red Hat. We track 8 published vulnerabilities in it, across 14 versions. None of them is on the list of flaws known to be exploited today. If you run Build of Keycloak, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Build of Keycloak vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Build of Keycloak's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Build of Keycloak flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 2.6%CVE-2024-7885High
A vulnerability was found in Undertow where the ProxyProtocolReadListener reuses the same StringBuilder instance across multiple requests.
- 2.1%CVE-2024-8883Medium
A misconfiguration flaw was found in Keycloak.
- 1.1%CVE-2026-7507High
A session fixation vulnerability was found in Keycloak's login-actions endpoints.
- 1.0%CVE-2026-7307High
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.
- 0.9%CVE-2026-2575Medium
A flaw was found in Keycloak. An unauthenticated remote attacker can trigger an application level Denial of Service (DoS) by sending a highly compressed SAMLRequest through the SAML Redirect Binding.
- 0.9%CVE-2026-4634High
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.
- 0.8%CVE-2024-7341High
A session fixation issue was discovered in the SAML adapters provided by Keycloak.
- 0.8%CVE-2024-4629Medium
A vulnerability was found in Keycloak. This flaw allows attackers to bypass brute force protection by exploiting the timing of login attempts.
- 0.7%CVE-2024-10234Medium
A vulnerability was found in Wildfly, where a user may perform Cross-site scripting in the Wildfly deployment system.
- 0.6%CVE-2024-7260Medium
An open redirect vulnerability was found in Keycloak.
Running Build of Keycloak? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Build of Keycloak on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 8 published vulnerabilities listed under the name Build of Keycloak, across 14 versions.
None of Build of Keycloak's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Build of Keycloak. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.