Quick answers
- Is CVE-2026-18207 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-18207 being exploited in the wild.
- How severe is CVE-2026-18207?
- Medium severity, with a CVSS score of 6.5, published 29 July 2026.
- Which products and versions are affected?
- Red Hat build of Keycloak All versions.
- Is there a fix for CVE-2026-18207?
- 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-18207 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-18207?
- Check whether you run Red Hat build of Keycloak at an affected version. 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
An improper authorization vulnerability (CWE-285) exists in Keycloak's client policy enforcement mechanism. The root cause is the system's reliance on group names rather than unique identifiers when validating group membership for policy enforcement. A remote attacker with low-level client management privileges can exploit this by joining or creating a group with a name that matches a privileged group in a different branch of the group hierarchy. This bypass allows the attacker to register or update clients while circumventing mandatory security hardening profiles. The vulnerability is tracked as CVE-2026-18207 and affects the Red Hat Build of Keycloak.
Affected products
- Red Hat Red Hat Build of Keycloak All versions
Timeline
- 2026-07-29: disclosed: Initial publication of the CVE record.
- 2026-07-29: advisory: Advisory published by Red Hat.