CVE-2026-18573
mediumpriority · track · 0OT risk · elevatedEPSS 0.005 · 41 %ileDEEUUSEPSS · scored 2026-10-27
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (3)
Products and version ranges known to be affected.
advisories (2)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2026-2614Keycloak: Mehrere SchwachstellenDeutsch2026-08-02csaf · cert_bundDE
Ein Angreifer kann mehrere Schwachstellen in Keycloak ausnutzen, um seine Privilegien zu erhöhen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren und sensible Informationen offenzulegen.
- BIT-keycloak-2026-18573Keycloak-services: keycloak-services: client access-type policy condition bypass during client update2026-08-31vendor · osvUS
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.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (8)
External citations — patches, advisories, analysis.
- https://access.redhat.com/security/cve/CVE-2026-18573cnnvd
- https://bugzilla.redhat.com/show_bug.cgi?id=2509764cnnvd
- https://access.redhat.com/security/cve/CVE-2026-18573enisa_euvd
- https://bugzilla.redhat.com/show_bug.cgi?id=2509764enisa_euvd
- https://access.redhat.com/errata/RHSA-2026:68277nvd
- https://access.redhat.com/errata/RHSA-2026:68278nvd
- https://access.redhat.com/security/cve/CVE-2026-18573Vendor Advisorynvd
- https://bugzilla.redhat.com/show_bug.cgi?id=2509764Issue TrackingVendor Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan