Quick answers
- Is CVE-2026-18573 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-18573 being exploited in the wild.
- How severe is CVE-2026-18573?
- Medium severity, with a CVSS score of 6.5, published 2 August 2026.
- Which products and versions are affected?
- Keycloak Keycloak.
- Is there a fix for CVE-2026-18573?
- 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-18573 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-18573?
- 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 vulnerability is a policy enforcement bypass in the keycloak-services component affecting client policy evaluation during client state updates. An attacker with client management permissions can circumvent realm administrator-configured client policies by exploiting improper validation during the transition from public to confidential client mode. The attack requires authenticated access (client management role) and proceeds by creating a public client and then updating it to confidential status with relaxed authentication settings. This allows persistence of clients that violate the realm's intended security hardening policies. A fix is expected to improve state validation during client updates.
Affected products
- Keycloak Keycloak
Timeline
- 2026-08-02: disclosed