Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-7504 high CVSS 8.1

Open Redirect in org.keycloak:keycloak-services (CVE-2026-7504)

Summary

Vulnerability in org.keycloak:keycloak-services (CVE-2026-7504). Confidential information can be exposed externally. Mitigation: upgrade to 26.6.2 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-7504 has been found in org.keycloak:keycloak-services.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade org.keycloak:keycloak-services to 26.6.2 or later.
If unsure, ask your IT team or search "org.keycloak:keycloak-services CVE-2026-7504" on the vendor's site.

CVE-2026-7504 (org.keycloak:keycloak-services) — CWE-601 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated
Patched: 26.6.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-601) exists in org.keycloak:keycloak-services.

📍 Affected scope

Check the vendor advisory for the affected versions of org.keycloak:keycloak-services.

🔥 Severity

Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 26.6.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.keycloak:keycloak-services を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.keycloak:keycloak-services to 26.6.2

    ステージング環境で 26.6.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.keycloak:keycloak-services
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"26.6.2"}]}]
Bitnami keycloak
[{"type":"SEMVER","events":[{"introduced":"26.4.0"},{"fixed":"26.4.12"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details