How severe is CVE-2026-18573?

CVE-2026-18573 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.

Is CVE-2026-18573 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (13th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-18573?

CVE-2026-18573 affects Redhat Build Of Keycloak. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-18573?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2026-18573 published?

CVE-2026-18573 was published on 2026-08-02 and last updated on 2026-08-10.

CVE-2026-18573

CVE-2026-18573 is a medium-severity vulnerability in Redhat Build Of Keycloak with a CVSS 3.x base score of 6.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-862.

Key facts

Severity: Medium (CVSS 3.x base score 6.5)
EPSS exploit prediction: 0% (13th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-862
Affected product: Redhat Build Of Keycloak
Published: 2026-08-02
Last modified: 2026-08-10

Description

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.

Frequently asked questions

What is CVE-2026-18573?: 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.
How severe is CVE-2026-18573?: CVE-2026-18573 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2026-18573 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (13th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-18573?: CVE-2026-18573 affects Redhat Build Of Keycloak. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-18573?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2026-18573 published?: CVE-2026-18573 was published on 2026-08-02 and last updated on 2026-08-10.

References

Affected products (1)

cpe:2.3:a:redhat:build_of_keycloak:-:*:*:*:-:*:*:*

More vulnerabilities in Redhat Build Of Keycloak

CVE-2026-15572 — High (CVSS 8.8): A flaw was found in Keycloak's Dynamic Client Registration (DCR) security policy management. The "Allowed Protocol…
CVE-2026-3047 — High (CVSS 8.8): A flaw was found in org.keycloak.broker.saml. When a disabled Security Assertion Markup Language (SAML) client is…
CVE-2026-16102 — High (CVSS 8.1): A flaw was found in the Dynamic Client Registration (DCR) component of Keycloak, an identity and access management…
CVE-2026-15573 — High (CVSS 8.1): A flaw was found in Keycloak's Authorization Services. The component responsible for matching request paths to security…
CVE-2026-1609 — High (CVSS 8.1): A flaw was found in Keycloak. When the JSON Web Token (JWT) authorization grant preview feature is enabled and a user…
CVE-2026-11800 — High (CVSS 8.1): A flaw was found in Keycloak. This JWT algorithm confusion vulnerability in the JWT Authorization Grant flow allows an…

All CVEs affecting Redhat Build Of Keycloak →

Other CWE-862 (Missing Authorization) vulnerabilities

CVE-2026-65667 — Critical (CVSS 10.0): Missing authorization in Microsoft Teams allows an unauthorized attacker to elevate privileges over a network.
CVE-2026-48168 — Critical (CVSS 10.0): PraisonAI is a multi-agent teams system. In versions prior to 4.6.40, the bundled Claude GitHub Actions workflow is…
CVE-2026-66012 — Critical (CVSS 10.0): SiYuan before v3.7.2 contains a missing authorization vulnerability in the POST /mcp kernel endpoint, which is gated…
CVE-2026-58275 — Critical (CVSS 10.0): Missing authorization in Azure DNS allows an unauthorized attacker to elevate privileges over a network.
CVE-2026-0092 — Critical (CVSS 10.0): In Package Manager, there is a possible device lock controller bypass due to a missing permission check. This could…
CVE-2026-33712 — Critical (CVSS 10.0): Typebot is a chatbot builder tool. In versions 3.15.2 and prior, the preview chat endpoint (POST…

Browse all CWE-862 (Missing Authorization) vulnerabilities →