Keycloak · Keycloak · published 2026-09-17

CVE-2026-90997Keycloak-services: keycloak: replay protection bypass leads to unauthorized access via database driver semantics mismatch

Routine No exploitation evidence; EPSS 0.4%.

CVE-2026-90997 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 34% of all CVEs. This Keycloak vulnerability: CVSS 7.4 (v3.1), a successful attack gives total control of the component. Fixed upstream in Keycloak 26.7.4. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Keycloak 26.7.4.

Patch events

  1. This monthSecurity release

    Identity & secretsKeycloak

    Keycloak security release: 26.7.4

    Upgrade to 26.7.4

    Why: Vendor security release for server software (most severe: CVE-2026-90997).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.4% (35th pct)FIRST EPSS v2026.06.15
CVSS base score7.4 (v3.1)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →