Skip to main content
VulnerabilityPublished Updated

CVE-2026-18211: Red Hat Build of Keycloak · Improper Input Validation

Affects Red Hat Build of KeycloakSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.2 Medium.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
4.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Red HatRed Hat Build of KeycloakAffected–Fixed in–
Red HatRed Hat Data Grid 8Affected–Fixed in–
Red HatRed Hat JBoss Enterprise Application Platform Expansion PackAffected–Fixed in–
Red HatRed Hat Single Sign-On 7Affected–Fixed in–

AI-suggested

Red Hat currently does not provide an official fix or mitigation that meets their criteria for ease of use, applicability, and stability. Users should monitor the Red Hat advisory for updates. Since exploitation requires Dynamic Client Registration to be enabled, disabling this feature where possible may reduce risk. Consult Red Hat support or a Technical Account Manager for tailored guidance.

Description

A flaw was found in the secure-client-uris client policy executor within Keycloak core services. This component is responsible for enforcing security requirements on client configurations, such as requiring encrypted connections for redirect URIs. Due to an improper check that only looks at the start of a web address rather than properly verifying the host, an attacker can bypass these security restrictions by using a specially crafted domain name. This could allow an attacker to intercept sensitive authentication codes over unencrypted connections.

References

Community reviews

Loading reviews…