CVE-2026-18201: Keycloak-services: keycloak-services: generic identity-provider creation can bind brokers to organizations without manage-organizations

Published Jul 29, 2026
·
Updated

A flaw was found in Keycloak. The generic identity-provider REST endpoint (/admin/realms/{realm}/identity-provider/instances) allows a user with only manage-identity-providers permission to bind a newly created identity provider to an organization by including an organizationId in the request payload. While the organization-scoped endpoint correctly requires both manage-identity-providers and manage-organizations permissions, the generic endpoint fails to enforce the manage-organizations check. This allows an IdP operator to associate brokers with organizations they are not authorized to manage, influencing organization login flows and broker selection. Additionally, this path skips organization IdP-list cache invalidation, making the newly bound broker invisible in cached organization IdP listings.

Other sources

Keycloak provides a way to manage identity providers and organizations through its administrative API. A flaw was discovered where an administrator with permission to manage identity providers could link a new provider to an organization without having the required permissions to manage that organization. This could allow an unauthorized administrator to influence how users log into specific organizations.

MITRE

Affected Software

2 affected components
Keycloak Keycloak
redhat Build Of Keycloak

Event History

Jul 29, 2026
Data Sourced
via Red Hat·07:42 AM
DescriptionSeverityAffected Software
CVE Published
via MITRE·08:34 AM
Data Sourced
via MITRE·08:34 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·10: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-18201?

CVE-2026-18201 has a medium severity score of 5.5.

2

How can CVE-2026-18201 be exploited?

CVE-2026-18201 can be exploited by a user with manage-identity-providers permission who can bind a new identity provider to an organization.

3

What permissions are required for CVE-2026-18201 exploitation?

Exploitation of CVE-2026-18201 requires only the manage-identity-providers permission.

4

How do I fix CVE-2026-18201?

To mitigate CVE-2026-18201, review and restrict permissions for users managing identity providers.

5

What software is affected by CVE-2026-18201?

CVE-2026-18201 affects Keycloak software specifically in its keycloak-services module.

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