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

Published Sep 14, 2026
·
Updated

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 Software

1 affected component
Keycloak Keycloak

Event History

Sep 14, 2026
Data Sourced
via Red Hat·03:02 PM
DescriptionSeverityAffected Software
Sep 17, 2026
CVE Published
via MITRE·06:47 PM
Data Sourced
via MITRE·06:47 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Does exploitation require attacker authentication or user interaction?

No. The severity vector indicates no privileges are required and no user interaction is required, although exploitation has high attack complexity.

2

Which deployments are exposed?

The affected scenario is Keycloak deployed in stateless mode with MySQL or MariaDB. The described impact is replay of intercepted single-use artifacts against the token endpoint or login flow.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203