CVE-2026-18201VulnerabilityPublished 28 Jul 2026Updated 8 Nov 2026

Bundesamt für Sicherheit in der Informationstechnik Open Source · Keycloak: Mehrere Schwachstellen ermöglichen Umgehen von Sicherheitsvorkehrungen

Affects Bundesamt für Sicherheit in der Informationstechnik Open SourceSource GCVE Database

Authoritative record:CVE-2026-18201· Medium 5.5

Not known to be exploited · CVSS 5.5 Medium · fixed in 26.7.3 : update Bundesamt für Sicherheit in der Informationstechnik Open Source when convenient.

Data as of 9 Nov 2026, 14:48 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 26.7.3

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

bundesamt-f-r-sicherheit-in-de

What to do

Affected software

Product	Affected	Fixed in
Red HatRed Hat build of Keycloak 26.6	Affected–	Fixed in–
Red HatRed Hat build of Keycloak 26.6	Affected–	Fixed in–
Red HatRed Hat build of Keycloak 26.6.7	Affected–	Fixed in–
Red HatRed Hat Data Grid 8	Affected–	Fixed in–
Red HatRed Hat JBoss Enterprise Application Platform Expansion Pack	Affected–	Fixed in–
Red HatRed Hat Single Sign-On 7	Affected–	Fixed in–

AI-suggested

A fix is available in Keycloak version 26.7.3. Users should upgrade to this version to remediate the vulnerabilities. Before applying the update, back up existing installations, including applications, configuration files, and databases. No vendor advisory indicates that no action is required or that the issues are already mitigated; therefore, upgrading is the recommended mitigation.

Description

Multiple vulnerabilities in Keycloak versions prior to 26.7.3 allow bypassing of security controls, including privilege escalation, information disclosure, unauthorized access, and remote code execution. These issues affect the Red Hat build of Keycloak and are addressed in version 26.7.3. The vulnerabilities include flaws in group hierarchy search, authorization code handling, JWT assertion policy, role authorization, impersonation, file read access, identity-provider creation, and others.

Impact

The vulnerabilities collectively allow unauthorized privilege escalation, information disclosure of sensitive data such as hidden groups and reCAPTCHA secrets, unauthorized creation of members, bypass of authorization policies, remote unauthenticated file reads, and remote code execution. These impacts can lead to full compromise of Keycloak authentication services, potentially affecting all applications relying on it for identity and access management.

Summary

Keycloak, an open-source identity and access management solution, has multiple security vulnerabilities affecting versions before 26.7.3. These vulnerabilities enable attackers to bypass security mechanisms such as authorization checks, impersonate realm administrators, disclose sensitive information, and execute remote code. The Red Hat advisories detail numerous CVEs fixed in version 26.7.3, including CVE-2026-18201 which allows generic identity-provider creation to bind brokers to organizations without proper permissions. The vendor has released updated packages and images for Red Hat builds of Keycloak 26.6.7 and 26.7.3 to address these issues.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Nov 2026, 14:48 UTC

Technical details

References

Community reviews

Related threats