CVE-2026-133705: Hanko before 3.2.0 Account Takeover via SAML Redirect Allowlist Bypass
Hanko before 3.2.0 contains an open redirect vulnerability in Saml.IsAllowedRedirect that allows unauthenticated attackers to bypass the redirect allowlist by appending attacker-controlled domain suffixes to allowed hostnames. Attackers can lure victims through a crafted /saml/auth login link to capture the one-time hankotoken and redeem it without PKCE to hijack the victim's session.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.2.0
Event History
Frequently Asked Questions
Who can exploit this issue?
An unauthenticated attacker can exploit it, but must convince a victim to follow a crafted /saml/auth login link. Successful exploitation depends on capturing the victim's one-time hanko_token from the redirect and redeeming it without PKCE.
Are default deployments affected?
The available information identifies affected versions as Hanko before 3.2.0, but does not state whether the vulnerable SAML redirect behavior is enabled or reachable in a default configuration. Deployments using the SAML authentication flow should treat versions before 3.2.0 as exposed.
How can I determine whether my deployment is affected?
Check the deployed Hanko version and the SAML configuration. Versions before 3.2.0 that process /saml/auth requests and rely on the redirect allowlist implemented by Saml.IsAllowedRedirect are affected.
What mitigation is available if an immediate upgrade is not possible?
The provided information does not specify a workaround. Reducing exposure to the SAML /saml/auth flow and preventing users from following untrusted login links may limit exploitation until Hanko can be updated to 3.2.0 or later.