← Search results
CVE-LINKED INVENTORY36 SECURITY RECORDS
Publisher not identified
keycloak
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at keycloak, but registry activity is not a publisher support boundary.
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-2023-4918 | 12 Sep 2023 | See the vendor and CVE records for the affected range. | 22.0.3 | Update reference ↗ |
| CVE-2023-1664 | 26 May 2023 | NA | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2022-1274 | 29 Mar 2023 | unknown | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-2237 | 27 Mar 2023 | unknown | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2022-2256 | 1 Sep 2022 | keycloak as shipped in Red Hat Single Sign-On 7 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2022-0225 | 26 Aug 2022 | Not-Known | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2021-3632 | 26 Aug 2022 | Fixed in v15.1.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-3754 | 26 Aug 2022 | Not-Known | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-3856 | 26 Aug 2022 | Fixed in 15.1.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-35509 | 23 Aug 2022 | 11.0.3, 12.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-3827 | 23 Aug 2022 | Fixed in v18.0.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-3513 | 22 Aug 2022 | Fixed in keycloak v13.0.0. | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-2668 | 5 Aug 2022 | Keycloak 18 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2022-1245 | 7 Jul 2022 | keycloak versions prior to 18.0.0 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2021-3461 | 1 Apr 2022 | rh-sso7-keycloak 9.0.13 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-4133 | 25 Jan 2022 | keycloak 15.1.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-3424 | 1 Jun 2021 | as shipped in Red Hat Single Sign-On 7.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-20195 | 28 May 2021 | keycloak 13.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-27826 | 28 May 2021 | keycloak 12.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-20202 | 12 May 2021 | keycloak 13.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-20222 | 23 Mar 2021 | keycloak 13.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-20262 | 9 Mar 2021 | Keycloak 12.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-27838 | 8 Mar 2021 | keycloak 13.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-14359 | 23 Feb 2021 | all versions as of 2021-02-22 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-10734 | 11 Feb 2021 | As shipped with Red Hat Fuse 7, Red Hat Single Sign-on 7, and Red Hat Openshift Application Runtimes | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-1717 | 11 Feb 2021 | keycloak 7.0.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-1725 | 28 Jan 2021 | keycloak 13.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-14302 | 15 Dec 2020 | keycloak 13.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-10770 | 15 Dec 2020 | keycloak 13.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-10776 | 17 Nov 2020 | before version 12.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2020-14389 | 17 Nov 2020 | before version 12.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-1694 | 16 Sep 2020 | all versions before 10.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-10748 | 16 Sep 2020 | keycloak 10.0.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-10758 | 16 Sep 2020 | Keycloak before 11.0.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2019-14910 | 5 Dec 2019 | n/a | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2019-14909 | 4 Dec 2019 | n/a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
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.