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.
CVE-2026-18201
Score 5.5 from GitHub Security Advisory published 2026-07-29. a secondary CVSS source baseline 5.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.5
- EG Score
- 5.5(high)
- EG Risk
- 25(Track)EG Risk 25/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity55% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 22%
- KEV
- Not listed
Published
July 29, 2026
Last Modified
July 30, 2026
Advisory Details (2)
Auto-updated Jul 29, 20262508290 – (CVE-2026-18201) CVE-2026-18201 keycloak-services: keycloak-services: Generic identity-provider creation can bind brokers to organizations without manage-organizations
https://bugzilla.redhat.com/show_bug.cgi?id=2508290Vendor Advisories for CVE-2026-18201(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-31 12:42 UTCEG score recompute
- 2026-07-31 12:42 UTCGHSA enrichment
- 2026-07-30 14:38 UTCGHSA enrichment
- 2026-07-30 12:26 UTCEG score recompute
- 2026-07-30 12:26 UTCGHSA enrichment
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 14:20 UTCEG score recompute
- 2026-07-29 14:20 UTCGHSA enrichment
- 2026-07-29 13:58 UTCEG score recompute
- 2026-07-29 13:58 UTCGHSA enrichment
- 2026-07-29 10:30 UTCEG score recompute
- 2026-07-29 09:28 UTCEG score recompute
- 2026-07-29 09:27 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-18201?
When was CVE-2026-18201 disclosed?
Is CVE-2026-18201 actively exploited?
What is the CVSS score of CVE-2026-18201?
How do I remediate CVE-2026-18201?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-18201
Is Your Infrastructure Affected by CVE-2026-18201?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.