CVE-2026-18573: Keycloak-services: client access-type policy condition bypass during client update
Red Hat · Red Hat build of Keycloak 26.6
Vendor fix available · Affected: Red Hat build of Keycloak 26.6 · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 42% of scored CVEs
DescriptionCVE.org
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.
Affected products9
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Red Hat · Red Hat build of Keycloak 26.6Versions not stated
- Red Hat · Red Hat build of Keycloak 26.6Versions not stated
- Red Hat · Red Hat build of Keycloak 26.6Versions not stated
- Red Hat · Red Hat build of Keycloak 26.6.7Versions not stated
- Red Hat · Red Hat build of Keycloak 26.6.7Versions not stated
- Red Hat · Red Hat build of Keycloak 26.6.7Versions not stated
- Red Hat · Red Hat Data Grid 8Versions not stated
- Red Hat · Red Hat JBoss Enterprise Application Platform Expansion PackVersions not stated
- Red Hat · Red Hat Single Sign-On 7Versions not stated
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Red Hat
- Published
- August 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-18573 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.