Quick answers
- Is CVE-2026-118030 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118030 being exploited in the wild.
- How severe is CVE-2026-118030?
- Medium severity, with a CVSS score of 4.2, published 29 October 2026.
- Which products and versions are affected?
- Red Hat Keycloak.
- Is there a fix for CVE-2026-118030?
- 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-118030 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-118030?
- Check whether you run Red Hat 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 race condition (CWE-362) exists in Keycloak's HOTP authentication component where validation of the one-time password and incrementation of the internal counter occur in two separate, non-atomic steps without proper synchronization. An attacker with a user's password can exploit the timing gap between validation and counter update to reuse the same OTP code across multiple concurrent login attempts. The vulnerability requires low privileges (valid credentials) and high attack complexity due to the race condition requirement, but introduces both confidentiality and integrity impacts.
Affected products
- Red Hat Keycloak
Timeline
- 2026-10-29: disclosed