Synced 17 Sept 2026 15:07 UTC Account
← Keycloak

Keycloak vulnerabilities: known CVEs & security history

Red Hat · Identity · 6 tracked CVEs · 0 actively exploited · updated September 2026 · what is a CVE? →

This is the full list of known vulnerabilities (CVEs) across all Keycloak release lines — 6 in total. A CVE here doesn't mean your version is affected — check Keycloak's current status and the safe version to run.

6
known CVEs
0
actively exploited (KEV)
0
critical severity
0
ransomware-linked

Known Keycloak CVEs

Actively-exploited and most-severe first. Open any CVE for full details.

CVESeverityCVSSEPSSYear
CVE-2026-3047 high 8.8 0% 2026
CVE-2024-1132 high 8.1 2% 2024
CVE-2025-7365 high 7.1 0% 2025
CVE-2024-7341 high 7.1 1% 2024
CVE-2025-8419 medium 5.3 0% 2025
CVE-2025-12150 low 3.1 0% 2026

Is my Keycloak version affected?

The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.

Check your Keycloak version → · Monitor Keycloak for new CVEs →

Keycloak vulnerabilities — frequently asked

How many known vulnerabilities does Keycloak have?

IsItPatched tracks 6 CVEs for Keycloak. 0 are critical-severity and 4 high-severity. These span every release line — what matters is whether the version you run is affected.

Does Keycloak have any actively-exploited vulnerabilities?

None of Keycloak's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.

What is the most severe Keycloak vulnerability?

Among tracked issues, CVE-2026-3047 (HIGH, CVSS 8.8) ranks highest — a CWE-305 weakness.

Is Keycloak safe to use?

It depends on the version. The latest supported Keycloak release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.

CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Keycloak security status · Keycloak end-of-life · actively-exploited CVEs. Always verify against Red Hat's advisories — see our disclaimer.