Skip to main content

Keycloak CVE-2026-18573

| EUVDEUVD-2026-51927 MEDIUM
Missing Authorization (CWE-862)
2026-08-02 redhat GHSA-wm3j-jpqg-fwv2
6.5
CVSS 3.1 · Vendor: redhat
Share

Severity by source

Vendor (redhat) PRIMARY
6.5 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
vuln.today AI
6.5 MEDIUM

Network-accessible admin API requires manage-clients role (PR:L); two-step manipulation is mechanically straightforward (AC:L); impact is integrity-only with no data disclosure or service disruption.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Red Hat
6.5 MEDIUM
qualitative

Primary rating from Vendor (redhat).

CVSS VectorVendor: redhat

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

Lifecycle Timeline

2
Analysis Generated
Aug 02, 2026 - 06:31 vuln.today
CVE Published
Aug 02, 2026 - 05:28 nvd
MEDIUM 6.5

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.

AnalysisAI

Client policy enforcement in Red Hat Build of Keycloak can be bypassed by an authenticated user holding client management permissions, allowing non-compliant OAuth clients to persist in a realm despite administrator-configured security hardening. The bypass exploits improper client state evaluation during update operations: an attacker creates a public client - which passes policy validation - and then updates it to a confidential client type, skipping the re-evaluation that would normally reject a non-compliant confidential client. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
Obtain manage-clients role in target realm
Delivery
Create new OAuth client with public type
Exploit
Client policy validation passes (public client exempt)
Execution
Update client type to confidential via admin API
Persist
Policy re-evaluation skipped during update operation
Impact
Non-compliant confidential client persists in realm

Vulnerability AssessmentAI

Exploitation Exploitation requires the attacker to hold client management permissions within the target Keycloak realm, specifically the manage-clients role or an equivalent delegated realm administrator capability that permits both client creation and client updates. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The CVSS 3.1 score of 6.5 with vector AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N accurately captures a medium-severity, network-accessible integrity bypass that requires low-privilege authenticated access. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario A developer or DevOps engineer holding the manage-clients role in a Keycloak realm - a common delegation in CI/CD-heavy environments - creates a new OAuth client as type public, which passes all client policy checks since policies are scoped to confidential clients. The attacker then calls the Keycloak admin REST API to update that client's type to confidential, at which point the server skips re-evaluation of the applicable client policies. …
Remediation Consult the Red Hat security advisory at https://access.redhat.com/security/cve/CVE-2026-18573 for patch availability; no specific fixed version was identified in the available intelligence data, so the exact remediated release must be confirmed directly with Red Hat. … Detailed patch versions, workarounds, and compensating controls in full report.

Threat intelligence, references, and detailed analysis are available after sign-in.

CVE-2026-16442 CRITICAL
9.8 Aug 05

Account takeover in Keycloak (Red Hat build of Keycloak, Red Hat Single Sign-On 7) arises because the IdP-initiated SAML

CVE-2026-18963 CRITICAL
9.1 Aug 18

Account takeover in Red Hat Build of Keycloak allows an unauthenticated attacker to abuse the reset-credentials flow in

CVE-2026-16443 CRITICAL
9.1 Aug 05

Authentication bypass in Red Hat Build of Keycloak (and Red Hat Single Sign-On 7) lets an unauthenticated attacker forge

CVE-2026-15572 HIGH
8.8 Aug 05

Privilege escalation in Red Hat Build of Keycloak's Dynamic Client Registration (DCR) grants an attacker with low-privil

CVE-2026-9800 HIGH
8.1 Jun 25

Authorization bypass in the Keycloak Policy Enforcer allows any authenticated user to circumvent all enforced access con

CVE-2026-15573 HIGH
8.1 Aug 05

URI normalization bypass in Keycloak's Authorization Services PathMatcher allows authenticated low-privilege users to re

CVE-2026-16102 HIGH
8.1 Aug 05

Privilege escalation in Keycloak's Dynamic Client Registration (DCR) component allows attackers with standard user accou

CVE-2026-18214 HIGH
8.1 Jul 31

Token exchange in Keycloak bypasses Google Workspace domain allowlist restrictions, enabling any valid Google account ho

CVE-2026-11800 HIGH
8.1 Jun 25

Signature-verification bypass in Keycloak (and Red Hat's Keycloak-based products such as Red Hat Single Sign-On 7 and Re

CVE-2026-18215 HIGH
8.1 Jul 31

Tenant-restriction bypass in Keycloak's Microsoft identity provider integration allows attackers holding any valid Micro

CVE-2026-18967 HIGH
8.1 Aug 06

Session hijacking via SAML assertion replay in Keycloak's SAML broker component allows adjacent-network attackers to aut

CVE-2026-7504 HIGH
8.1 May 19

Open redirect in Red Hat build of Keycloak permits remote attackers to send victims to attacker-controlled hosts by abus

Vendor StatusVendor

Debian

Bug #1088287
keycloak
Release Status Fixed Version Urgency
open - -

Share

CVE-2026-18573 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy