Quick answers
- Is CVE-2026-112201 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112201 being exploited in the wild.
- How severe is CVE-2026-112201?
- Medium severity, with a CVSS score of 4.8, published 11 November 2026.
- Which products and versions are affected?
- Keycloak Keycloak.
- Is there a fix for CVE-2026-112201?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-112201 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-112201?
- Check whether you run Keycloak. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A synchronization error in the login-failure storage component causes a repetitive database lock when concurrent failed login attempts target the same account on MySQL/MariaDB deployments. The flaw results in legitimate login attempts being rejected and some failures not being recorded, degrading both user authentication and brute-force detection mechanisms. This affects multi-node Keycloak configurations using these specific database backends.
Affected products
- Keycloak Keycloak
Timeline
- 2026-11-11: disclosed