Keycloak
Keycloak
Open Source Identity and Access Management For Modern Applications and Services
26.8.1
- Release date
- October 13, 2026
- Security status
- 1 high-severity CVE tracked in the last 90 days. Current version not affected.
Source
GitHub API
Public release notes are linked for the latest stored release.
Release history
See the latest published releases stored for this product.
| Version | Published | Notes |
|---|---|---|
| 26.8.1 | 2026-10-13 | Release Notes |
| 26.8.0 | 2026-10-01 | Release Notes |
| 26.7.5 | 2026-09-30 | Release Notes |
| 26.7.4 | 2026-09-16 | Release Notes |
| 26.7.3 | 2026-08-31 | Release Notes |
| 26.7.2 | 2026-08-19 | Release Notes |
| 26.7.1 | 2026-08-05 | Release Notes |
| 26.7.0 | 2026-07-09 | Release Notes |
| 26.6.4 | 2026-06-26 | Release Notes |
| 26.6.3 | 2026-06-04 | Release Notes |
| 26.6.2 | 2026-05-19 | Release Notes |
| 26.6.1 | 2026-04-15 | Release Notes |
Vulnerability tracking
versionPing monitors CVEs for this product. Matching CVEs are listed below. We only display CVEs with a CVSS score of 7.0 or higher that were published within the last 90 days.
Affected status is inferred from published affected version ranges where available. Always verify against the vendor advisory before making production decisions.
| CVE | Severity | Published | Status | Summary |
|---|---|---|---|---|
| CVE-2026-90997 | HIGH (7.4) | 2026-09-17 | Current versionnot affected | A flaw was found in Keycloak. When deployed in stateless mode with MySQL or MariaDB, a mismatch in row-count semantics between the database driver and Keycloak's application logic allows an attacker to bypass replay protection. This vulnerability enables an attacker who intercepts single-use security artifacts, such as JWT client assertions, DPoP proofs, or one-time password (TOTP) codes, to replay them. Successful exploitation grants unauthorized access to the token endpoint or login flow. Affected versions
|