CVE-2026-7504

Org.keycloak/keycloak-services: open redirect when using wildcard valid redirect uris in keycloak

HIGH
8.1
CVSS Score
Published: May 19, 2026 at 11:01 AM UTC
Updated: October 26, 2026 at 01:10 PM UTC
1 product affected across 1 vendorBuild of Keycloak

Using Red Hat Build of Keycloak by Red Hat?

Get instant alerts when new vulnerabilities affect Red Hat Build of Keycloak - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.1
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

26.4 ≤ v < 26.4.12
Vendor states this is fixed in 26.2-21 (unaffected)
Vendor states this is fixed in 26.2.16 (unaffected)
Vendor states this is fixed in 26.2.16-1 (unaffected)
Vendor states this is fixed in 26.4-17 (unaffected)
Vendor states this is fixed in 26.4.12 (unaffected)
Vendor states this is fixed in 26.4.12-1 (unaffected)
Vendor states this is fixed in rhel9-operator (unaffected)

References (7)

VDB Entryx_refsource_REDHATVendor Advisory
Source: cverecord
https://access.redhat.com/security/cve/CVE-2026-7504
Issue Trackingx_refsource_REDHATVendor Advisory
Source: cverecord
https://bugzilla.redhat.com/show_bug.cgi?id=2464128
Vendor Advisoryx_refsource_REDHAT
Source: cverecord
https://access.redhat.com/errata/RHSA-2026:19594
Vendor Advisoryx_refsource_REDHAT
Source: cverecord
https://access.redhat.com/errata/RHSA-2026:19597
Vendor Advisoryx_refsource_REDHAT
Source: cverecord
https://access.redhat.com/errata/RHSA-2026:19595
Vendor Advisoryx_refsource_REDHAT
Source: cverecord
https://access.redhat.com/errata/RHSA-2026:19596

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.1HIGHredhat
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-601

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card