Low [CVE-2026-18217] SAML HTTP-Redirect binding response preserves query string leading to parameter pollution
This low-severity Red Hat Linux advisory covers CVE-2026-18217 affecting Red Hat Build of Keycloak.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
A flaw was found in the SAML protocol implementation of Keycloak, an open-source identity and access management solution. The issue occurs when Keycloak handles SAML authentication requests using the HTTP-Redirect binding.
If a client is configured with a wildcard redirect URL, an attacker can craft a request that includes malicious parameters. When a user authenticates, Keycloak appends its legitimate response to the attacker's parameters.
This can cause some service providers to process the attacker's data instead of the real login information, potentially leading to a user being logged into the wrong account.
The Red Hat Product Security team has assessed the severity of this vulnerability as Moderate, given that exploitation requires a specific client configuration (wildcard redirect URIs) and a downstream service provider that incorrectly handles duplicate HTTP parameters.
Successful exploitation allows an attacker to perform login CSRF or session swapping on the affected service provider. The vulnerability's root cause is the improper handling of the query string in the SAML HTTP-Redirect binding response, which fails to strip or validate pre-existing SAML parameters.
Weakness: CWE-20. Affected Red Hat products: Red Hat Build of Keycloak.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 9 days ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 9 days ago·verify at source
Mitigation checklist
- Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Official advisory · high-confidence parse· fetched 9 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.