CVSS 3.1
4.8 mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:LCVE-2026-112201 Keycloak-services: keycloak-services: login-failure upsert trusts mysql/mariadb affected-row count
Medium (4.8). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
A flaw was found in the login-failure storage component of Keycloak, the identity and access management solution. This issue specifically affects deployments using MySQL or MariaDB databases in a multi-node configuration. When multiple failed login attempts occur simultaneously for the same account, a synchronization error can cause the system to enter a repetitive loop that locks the user's record in the database. This results in legitimate login attempts for that user being blocked and failing with an error. Furthermore, because some failures are not correctly recorded during this loop, the system's brute-force protection may not accurately count all failed attempts.
Severity
- EPSS
- 0.2% estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
- OWASP Top 10
- A06:2025 Insecure Design
- Published
- Modified
- Assigned by
- redhat (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-112201 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-112201?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-112201?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-112201 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-112201)
HTML:
<a href="https://cve.bz/cve/CVE-2026-112201"><img src="https://cve.bz/cve/badge/CVE-2026-112201.svg" alt="CVE-2026-112201"></a>
Affected
- keycloak:keycloak-services
- red hat:red hat build of keycloak
- red hat:red hat single sign-on 7
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| keycloak-services | from 26.8.0 through 26.8.1 |
Attack patterns (CAPEC)
- CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
- CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.