https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 16:10:43 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-07782 bdu:2026-07782 https://cve.radiocsirt.org/vuln/bdu:2026-07782 https://cve.radiocsirt.org/vuln/bit-keycloak-2026-7504 <p><strong>Affected:</strong> Bitnami: keycloak</p> <p>A flaw was found in Keycloak&#39;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 &#34;Valid Redirect URIs&#34; field and requires user interaction to be successfully exploited.</p> <p>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&#39;s URI parser fails to extract the user-info, leaving only the raw authority field. Consequently, Keycloak&#39;s validation check fails to detect the malformed user-info, falls back to a wildcard comparison, and incorrectly permits the malicious redirect.</p> <p><strong>Affected:</strong> Bitnami: keycloak</p> <p>A flaw was found in Keycloak&#39;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 &#34;Valid Redirect URIs&#34; field and requires user interaction to be successfully exploited.</p> <p>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&#39;s URI parser fails to extract the user-info, leaving only the raw authority field. Consequently, Keycloak&#39;s validation check fails to detect the malformed user-info, falls back to a wildcard comparison, and incorrectly permits the malicious redirect.</p> https://cve.radiocsirt.org/vuln/bit-keycloak-2026-7504 https://cve.radiocsirt.org/vuln/euvd-2026-337153 EUVD-2026-337153 https://cve.radiocsirt.org/vuln/euvd-2026-337153 https://cve.radiocsirt.org/vuln/fkie_cve-2026-7504 <p>A flaw was found in Keycloak&#39;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 &#34;Valid Redirect URIs&#34; field and requires user interaction to be successfully exploited.</p> <p>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&#39;s URI parser fails to extract the user-info, leaving only the raw authority field. Consequently, Keycloak&#39;s validation check fails to detect the malformed user-info, falls back to a wildcard comparison, and incorrectly permits the malicious redirect.</p> <p>A flaw was found in Keycloak&#39;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 &#34;Valid Redirect URIs&#34; field and requires user interaction to be successfully exploited.</p> <p>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&#39;s URI parser fails to extract the user-info, leaving only the raw authority field. Consequently, Keycloak&#39;s validation check fails to detect the malformed user-info, falls back to a wildcard comparison, and incorrectly permits the malicious redirect.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-7504 https://cve.radiocsirt.org/vuln/ghsa-rp95-xpg9-c2cq <p><strong>Affected:</strong> Maven: org.keycloak:keycloak-services</p> <p>A flaw was found in Keycloak&#39;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 &#34;Valid Redirect URIs&#34; field and requires user interaction to be successfully exploited.</p> <p>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&#39;s URI parser fails to extract the user-info, leaving only the raw authority field. Consequently, Keycloak&#39;s validation check fails to detect the malformed user-info, falls back to a wildcard comparison, and incorrectly permits the malicious redirect.</p> <p><strong>Affected:</strong> Maven: org.keycloak:keycloak-services</p> <p>A flaw was found in Keycloak&#39;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 &#34;Valid Redirect URIs&#34; field and requires user interaction to be successfully exploited.</p> <p>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&#39;s URI parser fails to extract the user-info, leaving only the raw authority field. Consequently, Keycloak&#39;s validation check fails to detect the malformed user-info, falls back to a wildcard comparison, and incorrectly permits the malicious redirect.</p> https://cve.radiocsirt.org/vuln/ghsa-rp95-xpg9-c2cq https://cve.radiocsirt.org/vuln/rhsa-2026:19594 <p>keycloak: Keycloak: Denial of Service via specially crafted SAML input org.keycloak/keycloak-services: Open redirect when using wildcard valid redirect URIs in Keycloak org.keycloak/keycloak-services: Session fixation in OIDC login flow that can lead to account takeover</p> <p>keycloak: Keycloak: Denial of Service via specially crafted SAML input org.keycloak/keycloak-services: Open redirect when using wildcard valid redirect URIs in Keycloak org.keycloak/keycloak-services: Session fixation in OIDC login flow that can lead to account takeover</p> https://cve.radiocsirt.org/vuln/rhsa-2026:19594 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1612 <p>Ein Angreifer kann mehrere Schwachstellen in Keycloak ausnutzen, um Informationen offenzulegen, Daten zu manipulieren, Sicherheitsvorkehrungen zu umgehen und einen Denial of Service zu verursachen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Keycloak ausnutzen, um Informationen offenzulegen, Daten zu manipulieren, Sicherheitsvorkehrungen zu umgehen und einen Denial of Service zu verursachen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1612