REDHAT-BUG-2508292: Low severity Keycloak ClientUpdaterSourceHostsCondition vulnerability
A flaw was found in the hostname matching logic within the ClientUpdaterSourceHostsCondition of Keycloak. When a wildcard domain (e.g., .example.com) is configured as a trusted source host in a client policy, the matching mechanism performs a simple suffix check without ensuring a proper subdomain boundary (a preceding dot). An unauthenticated attacker whose connecting IP address reverse-resolves to a crafted hostname ending in the trusted suffix (e.g., attackerexample.com) can satisfy the condition. This allows the attacker to bypass source-host restrictions intended to limit client registration or update operations to trusted domains. Successful exploitation causes policy executors to run as if the request originated from a legitimate trusted source, which can weaken or bypass security constraints applied to client management.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
Review and remove any wildcard trusted source hosts configured in Keycloak client policies (e.g., remove patterns like *.example.com) to avoid suffix-only hostname matching that can be bypassed via crafted reverse-resolved hostnames.
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-2508292?
The severity of REDHAT-BUG-2508292 is classified as low.
What vulnerability does REDHAT-BUG-2508292 describe?
REDHAT-BUG-2508292 describes a flaw in the hostname matching logic within Keycloak's ClientUpdaterSourceHostsCondition.
How do I mitigate the risks associated with REDHAT-BUG-2508292?
To mitigate the risks associated with REDHAT-BUG-2508292, avoid using wildcard domains as trusted source hosts in client policies.
What software is affected by REDHAT-BUG-2508292?
REDHAT-BUG-2508292 affects the Keycloak ClientUpdaterSourceHostsCondition.
When was REDHAT-BUG-2508292 published?
REDHAT-BUG-2508292 was published on July 29, 2026.