Keycloak CVE-2026-7504: Critical URL Validation Bypass

Keycloak CVE-2026-7504: Critical URL Validation Bypass

A high-severity vulnerability, CVE-2026-7504, has been identified in Keycloak’s URL validation logic, according to the National Vulnerability Database. This flaw allows an attacker to bypass redirect validation, potentially leading to unauthorized redirects and the exposure of sensitive information within the domain, or facilitating further attacks. The exploit requires user interaction and specifically impacts Keycloak clients configured with a wildcard (*) in their “Valid Redirect URIs” field.

The root cause lies in a discrepancy between Keycloak’s validation and Java’s URI implementation. An attacker can craft a malicious redirect URL using multiple ‘@’ characters within the user-info component. Java’s URI parser then fails to extract the user-info, leaving only the raw authority field. Keycloak’s subsequent validation check misses the malformed user-info, falls back to a wildcard comparison, and erroneously permits the malicious redirect. This design oversight effectively nullifies the intended security control for certain configurations.

With a CVSS score of 8.1 (HIGH), this vulnerability presents a significant risk for organizations using vulnerable Keycloak configurations. The ability to redirect users to attacker-controlled pages within a trusted domain can be leveraged for sophisticated phishing, credential harvesting, or session hijacking attacks, making it a critical concern for identity and access management security.

What This Means For You

  • If your organization uses Keycloak, you must immediately audit your client configurations. Prioritize identifying any clients with a wildcard (*) in their "Valid Redirect URIs" field. These are directly vulnerable to CVE-2026-7504. Review all redirect logic and ensure strict validation is in place, moving away from broad wildcard configurations where possible. This isn't just about patching; it's about re-evaluating your redirect security posture.

Indicators of Compromise

IDTypeIndicator
CVE-2026-7504 Open Redirect Keycloak clients configured with a wildcard (*) in the "Valid Redirect URIs" field
CVE-2026-7504 Open Redirect Keycloak URL validation logic bypass
CVE-2026-7504 Open Redirect Malicious redirect URL constructed using multiple '@' characters in the user-info section
🔎
Keycloak Vulnerability Intel Use /brief to get an analyst-ready summary of high-severity vulnerabilities and their impact.
Open Intel Bot →
Source & Attribution
Source PlatformNVD
ChannelNational Vulnerability Database
PublishedMay 19, 2026 at 15:16 UTC

This content was AI-rewritten and enriched by Shimi's Cyber World based on the original source. All intellectual property rights remain with the original author.

Believe this infringes your rights? Submit a takedown request.

Related coverage

CVE-2026-20240 — Denial of Service

CVE-2026-20240 — In Splunk Enterprise versions below 10.2.2, 10.0.5, 9.4.11, and 9.3.12, and Splunk Cloud Platform versions below 10.4.2603.1, 10.3.2512.9, 10.2.2510.11, 10.1.2507.21, 10.0.2503.13, and 9.3.2411.129,...

vulnerabilityCVEmedium-severitydenial-of-servicecwe-20
/SCW Vulnerability Desk /MEDIUM /6.5 /⚑ 2 IOCs /⚙ 2 Sigma

Splunk Enterprise, Cloud Vulnerability Exposes Session Cookies, Sensitive Data

CVE-2026-20239 — In Splunk Enterprise versions below 10.2.2 and 10.0.5, and Splunk Cloud Platform versions below 10.3.2512.8, 10.2.2510.11, 10.1.2507.21, and 10.0.2503.13, a user with a...

vulnerabilityCVEhigh-severitycwe-532
/SCW Vulnerability Desk /HIGH /7.5 /⚑ 5 IOCs /⚙ 4 Sigma

CVE-2026-20238 — In Splunk AI Toolkit versions below 5.7.3, a low-privileged

CVE-2026-20238 — In Splunk AI Toolkit versions below 5.7.3, a low-privileged user that does not hold the 'admin' or 'power' roles could access confidential data...

vulnerabilityCVEmedium-severitycwe-863
/SCW Vulnerability Desk /MEDIUM /6.5 /⚑ 2 IOCs /⚙ 2 Sigma