Red Hat
Red Hat Build of Keycloak
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2025-2559 | 25 Mar 2025 | 23.0.0 < 26.0.11, 26.1.0 < 26.1.5 | Red Hat build of Keycloak 26.0: 26.0.11-2 < *, 26.0-12 < *, 26.0-13 < * | Update reference ↗ |
| CVE-2025-1391 | 17 Feb 2025 | 26.0.0 < 26.0.10 | Red Hat build of Keycloak 26.0: 26.0.10-3 < *, 26.0-11 < *, 26.0-12 < * | Update reference ↗ |
| CVE-2025-0604 | 22 Jan 2025 | < 26.0.10, < 26.1.3 | Red Hat build of Keycloak 26.0: 26.0.10-3 < *, 26.0-11 < *, 26.0-12 < * | Update reference ↗ |
| CVE-2024-3656 | 9 Oct 2024 | < 24.0.5 | Before applying the update, back up your existing installation, including all applications, configuration files, databases and database settings, and so on. | Update reference ↗ |
| CVE-2024-4540 | 3 Jun 2024 | See the vendor and CVE records for the affected range. | d5e82356f90893ca3b308a7e10020103e402369a < *; Red Hat build of Keycloak 22: 22.0.11-2 < *, 22-15 < *, 22-18 < *; Red Hat build of Keycloak 24: 24.0.5-2 < *, 24-10 < *; Red Hat Single Sign-On 7.6 for RHEL 7: 0:18.0.14-1.redhat_00001.1.el7sso < *; Red Hat Single Sign-On 7.6 for RHEL 8: 0:18.0.14-1.redhat_00001.1.el8sso < *; Red Hat Single Sign-On 7.6 for RHEL 9: 0:18.0.14-1.redhat_00001.1.el9sso < *; RHEL-8 based Middleware Containers: 7.6-49 < * | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.