CVE-2026-18211
Last modified
CVE-2026-18211 is a medium-severity vulnerability rated 5.4/10 on the CVSS scale. 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. EPSS estimates a 0.19% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Redhat | Build Of Keycloak | All versions |
References
- https://access.redhat.com/security/cve/CVE-2026-18211Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=2508306Issue Tracking, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-18211?
How severe is CVE-2026-18211?
How do I fix CVE-2026-18211?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-18203A flaw was found in the group policy evaluation logic of Key…6.5
- CVE-2026-18206A flaw was found in the keycloak-services component of Keycl…3.7
- CVE-2026-18207A flaw was found in the client policy enforcement mechanism …6.5
- CVE-2026-18208A flaw was found in the OIDC token introspection endpoint of…6.5
- CVE-2026-18209A flaw was found in the keycloak-services component of Keycl…4.7
- CVE-2026-1821The Microtango plugin for WordPress is vulnerable to Stored …6.4
- CVE-2026-18214Keycloak allows users to log in using Google accounts and ca…8.1
- CVE-2026-18215Keycloak provides a way to let users log in using Microsoft …8.1
- CVE-2026-18217A flaw was found in the SAML protocol implementation of Keyc…4.7
- CVE-2026-18218A flaw was found in the TokenManager component of the Keyclo…5.4
- CVE-2026-1822The WP NG Weather plugin for WordPress is vulnerable to Stor…6.4
- CVE-2026-18220An out-of-bounds write vulnerability was found in the BFD li…7.8
Are you affected by CVE-2026-18211?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
