CVE-2026-18206: Keycloak-services: keycloak-services: client policy source-host wildcard domain matching bypass

Published Jul 29, 2026
·
Updated

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.

Other sources

A flaw was found in the keycloak-services component of Keycloak, which provides identity and access management services. The issue occurs when a realm administrator uses a wildcard domain (like .example.com) to restrict which hosts can register or update clients. Due to improper validation, the system accepts any hostname that ends with the specified domain suffix, even if it is not a legitimate subdomain. An attacker who can control the reverse DNS of their connection can bypass these host-based restrictions, potentially allowing unauthorized client modifications.

MITRE

Affected Software

3 affected components
Keycloak Keycloak
Keycloak keycloak-services
redhat Build Of Keycloak

Event History

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

The severity of CVE-2026-18206 is classified as low with a score of 3.7.

2

How do I fix CVE-2026-18206?

To fix CVE-2026-18206, ensure that hostname matching logic is correctly validating wildcard domains against trusted source hosts.

3

What systems are affected by CVE-2026-18206?

CVE-2026-18206 affects Keycloak and specifically the keycloak-services module.

4

What is the nature of the vulnerability in CVE-2026-18206?

CVE-2026-18206 is a flaw in the hostname matching logic that allows wildcard domain matching bypass.

5

When was CVE-2026-18206 published?

CVE-2026-18206 was published on July 29, 2026.

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