LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-7504 is an open redirect flaw in Red Hat build of Keycloak. It matters when clients allow wildcard redirect URIs. A user can be tricked into following a crafted login or redirect flow that sends them to an unauthorized URL, increasing phishing and sensitive-information exposure risk.

Executive priority

Treat this as a high-priority identity-platform configuration and patching issue. It is not reported as actively exploited in the provided sources, but affected SSO systems can amplify phishing and credential-risk scenarios across many applications.

Technical view

Keycloak redirect validation can disagree with Java URI parsing when a URL contains malformed user-info with multiple @ characters. In affected wildcard redirect configurations, Keycloak may fall back to wildcard matching and allow a redirect it should reject. The issue is classified as CWE-601 with CVSS 8.1.

Likely exposure

Exposure appears limited to Red Hat build of Keycloak 26.2 and 26.4 deployments using affected packages and clients configured with wildcard (*) Valid Redirect URIs. Deployments without wildcard client redirects are less likely to be exposed based on the provided description.

Exploitation context

The source bundle says exploitation requires user interaction. KEV is false, and no cited source in the bundle states active exploitation. The main risk is redirect abuse that supports phishing, token or information exposure, or follow-on attacks within trusted authentication flows.

Researcher notes

Focus validation on the intersection of affected Red Hat build of Keycloak versions and wildcard redirect URI client configuration. Evidence in the bundle is sufficient for exposure triage, but operational fix details should be confirmed against the linked Red Hat advisories.

Mitigation direction

  • Apply the relevant Red Hat advisories or vendor-recommended updates.
  • Replace wildcard Valid Redirect URIs with explicit allowed redirect URLs.
  • Audit Keycloak clients for unnecessary wildcard redirect configuration.
  • Prioritize internet-facing identity providers and high-value client applications.
  • Monitor authentication logs for unexpected redirect destinations.

Validation and detection

  • Inventory Red Hat build of Keycloak 26.2 and 26.4 deployments.
  • Check installed packages against the affected and unaffected versions listed by Red Hat.
  • Review every client for wildcard (*) Valid Redirect URIs.
  • Confirm redirects only resolve to explicitly intended application URLs.
  • Review recent auth events for unusual redirect_uri values or unauthorized destinations.
Prepared
Confidence
high
Sources
9

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-601: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-7504 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
7Timeline events
2ADP providers
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N2.85.2redhat
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N2.85.2redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2026-7504Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. ADP timelineredhat-SADP

    Reported to Red Hat.

  2. Source timelineredhat

    Reported to Red Hat.

  3. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  4. ADP timelineredhat-SADP

    Made public.

  5. Source timelineredhat

    Made public.

  6. CVE publishedCVE Program

    The CVE record was published.

  7. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPorg.keycloak/keycloak-services: Open redirect when using wildcard valid redirect URIs in Keycloak
other:Red Hat severity ratingcvssV3_1
  • 2026-04-30T14:46:59.812Z: Reported to Red Hat.
  • 2026-05-19T10:52:12.777Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Red HatRed Hat build of Keycloak 26.2rhbk/keycloak-operator-bundle, 26.2.16-1affected
Red HatRed Hat build of Keycloak 26.2rhbk/keycloak-rhel9, 26.2-21affected
Red HatRed Hat build of Keycloak 26.2rhbk/keycloak-rhel9-operator, 26.2-21affected
Red HatRed Hat build of Keycloak 26.2.16rhbk/keycloak-rhel9-operatorunaffected
Red HatRed Hat build of Keycloak 26.4rhbk/keycloak-operator-bundle, 26.4.12-1affected
Red HatRed Hat build of Keycloak 26.4rhbk/keycloak-rhel9, 26.4-17affected
Red HatRed Hat build of Keycloak 26.4rhbk/keycloak-rhel9-operator, 26.4-17affected
Red HatRed Hat build of Keycloak 26.4.12rhbk/keycloak-rhel9-operatorunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-601 · source CWE mapping

URL Redirection to Untrusted Site ('Open Redirect')

URL Redirection to Untrusted Site ('Open Redirect') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.