Intel

AIKIDO-2026-614276

keycloak-model-jpa is vulnerable to Denial of Service (DoS)

CVE-2026-112201Published 4 days ago
November 16, 2026

48

CVE Score

Medium

Denial of Service (DoS)

Are you affected? Scan for Free

TL;DR

Keycloak's persistent login-failure provider trusts the affected-row count returned by a MySQL or MariaDB upsert and can repeatedly read a stale snapshot when a concurrent transaction inserted the same record. Concurrent failed logins can leave the provider retrying while holding database resources, blocking legitimate logins and failing to record some attempts used by brute-force protection.

How do I fix this?

Upgrade org.keycloak:keycloak-model-jpa to the patched version. The fix uses a pessimistic current read when the database's upsert row count is unreliable, bounds retries, and preserves the lock state when refreshing a login-failure record.

Who does this affect?

You are affected if you use a vulnerable version of org.keycloak:keycloak-model-jpa for persistent login-failure storage on MySQL or MariaDB and concurrent login attempts can occur for the same account, particularly in a multi-node deployment.

Versions

26.8.0 - 26.8.1

Fixed in 26.8.2

Background info

keycloak-model-jpa is vulnerable to Denial of Service (DoS) in versions 26.8.0 - 26.8.1.

Get secure today,
quickly and for free.

Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.

No credit card required | Scan results in 32 seconds.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea