Quick answers
- Is CVE-2026-103112 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103112 being exploited in the wild.
- How severe is CVE-2026-103112?
- High severity, with a CVSS score of 7.5, published 5 November 2026.
- Which products and versions are affected?
- Keycloak.
- Is there a fix for CVE-2026-103112?
- 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-103112 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-103112?
- 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
The keycloak-services component fails to verify that an authenticator is valid for the current authentication flow when switching between standard authentication and reset credentials paths. An authenticated attacker can trigger a race condition during credential reset to associate their authentication state with another user's session, bypassing access controls. This is a CWE-362 concurrent execution vulnerability requiring low privilege, network access, but high attack complexity due to the race condition requirement.
Affected products
- Keycloak
Timeline
- 2026-11-05: disclosed