CVE-2026-18573: Keycloak-services: keycloak-services: client access-type policy condition bypass during client update

Published Jul 31, 2026
·
Updated

A flaw was found in the keycloak-services component of Keycloak, which is used for managing authentication and authorization flows. The issue occurs when a realm administrator configures client policies to enforce specific authentication requirements on confidential clients. Due to improper evaluation of the client state during an update operation, an attacker with client management permissions can bypass these security policies by first creating a public client and then updating it to a confidential client with weaker authentication. This can result in the persistence of clients that do not comply with the intended security hardening of the realm.

Other sources

A state-based policy bypass vulnerability was discovered in Keycloak's client policy engine. The flaw exists in the way the access-type condition evaluates UPDATE operations. Specifically, the condition checks the old client state instead of the proposed new state during an update. An attacker with low privileges, such as delegated client management permissions or a valid dynamic registration token, can exploit this by creating a public client and subsequently updating it to a confidential client. Because the policy engine still perceives the client as public during the update process, it fails to trigger the confidential-client policy profile. This allows the attacker to configure a confidential client with weak authentication (e.g., client-secret) even when the realm policy mandates stronger methods like client-jwt. Successful exploitation allows an attacker to persist non-compliant confidential clients, undermining realm-level security hardening.

Red Hat

Affected Software

3 affected components
Keycloak
Keycloak client policy engine
redhat Build Of Keycloak

Event History

Jul 31, 2026
Data Sourced
via Red Hat·12:37 PM
DescriptionSeverityAffected Software
Aug 2, 2026
CVE Published
via MITRE·05:28 AM
Data Sourced
via MITRE·05:28 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:16 AM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-18573?

The severity of CVE-2026-18573 is rated as medium with a score of 6.5.

2

How do I fix CVE-2026-18573?

To fix CVE-2026-18573, update Keycloak to the latest version that contains the security patch.

3

What types of systems are affected by CVE-2026-18573?

CVE-2026-18573 affects systems using Keycloak services for managing authentication and authorization.

4

What is the impact of CVE-2026-18573?

CVE-2026-18573 can lead to a bypass of client access-type policies configured by realm administrators.

5

Who is at risk due to CVE-2026-18573?

Realm administrators managing confidential clients within Keycloak are at risk due to CVE-2026-18573.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203