dbcve.org
Build Of KeycloakApplication · Redhat

CVE-2026-7504

HIGH · 8.1 CVSS v3.1 Published 2026-05-19
Fix available
A fix is available. Upgrade to 26.4.12 or later.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw was found in Keycloak's URL validation logic during redirect operations. By crafting a malicious request, an attacker could bypass validation to redirect users to unauthorized URLs, potentially leading to the exposure of sensitive information within the domain or facilitating further attacks. This vulnerability specifically affects Keycloak clients configured with a wildcard (*) in the "Valid Redirect URIs" field and requires user interaction to be successfully exploited. The issue stems from a discrepancy in how Keycloak and the underlying Java URI implementation handle the user-info component of a URL. If a malicious redirect URL is constructed using multiple @ characters in the user-info section, Java's URI parser fails to extract the user-info, leaving only the raw authority field. Consequently, Keycloak's validation check fails to detect the malformed user-info, falls back to a wildcard comparison, and incorrectly permits the malicious redirect.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Keycloak's URL validation has a bypass vulnerability where crafted URLs with multiple @ characters in the user-info section cause Java's URI parser to fail extracting user-info, leaving raw authority. Keycloak's validator then falls back to wildcard comparison and incorrectly allows the malicious redirect. This only affects clients using wildcard (*) in Valid Redirect URIs and requires user interaction.

MitigationRemove wildcard (*) configurations from Valid Redirect URIs in all Keycloak clients and replace with specific, explicit redirect URIs. Review existing client configurations for wildcard usage.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Build Of KeycloakApplication
Affected:>= 26.4, < 26.4.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Keycloak version
    Run 'kc.sh version' or check the /opt/keycloak/bin/kc.sh version, or inspect the keycloak-version in the container/package metadata
    Affected if The installed version is >= 26.4 and < 26.4.12
  2. Identify clients with wildcard redirect URIs
    Query the Keycloak database or use admin console to list all clients and inspect the 'redirectUris' or 'validRedirectUris' attribute for each client. Look for entries containing '*' as the entire value or as a wildcard pattern
    Affected if Any client has a wildcard (*) configured in Valid Redirect URIs

Environment is affected if Keycloak version is between 26.4 and 26.4.11 inclusive AND at least one client is configured with wildcard (*) in Valid Redirect URIs

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 26.4.12 or later
Fixed in 26.4.12
Interim mitigation

Remove wildcard (*) configurations from Valid Redirect URIs in all Keycloak clients and replace with specific, explicit redirect URIs. Review existing client configurations for wildcard usage.

Recommended fix Moderate confidence

26.4.12

  1. 1. Identify all Keycloak instances running version 26.4.x where 26.4 <= version < 26.4.12
  2. 2. Review all client configurations that use wildcard (*) in the 'Valid Redirect URIs' field
  3. 3. Schedule a maintenance window for the upgrade
  4. 4. Back up the Keycloak database and configuration
  5. 5. Upgrade Keycloak to version 26.4.12 or later
  6. 6. After upgrade, verify that open redirect validation works correctly by testing with crafted URLs containing multiple @ characters in the user-info section
  7. 7. Consider restricting wildcard redirect URIs to specific legitimate domains as a defense-in-depth measure

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Build Of Keycloak Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7504 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7504 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data