Hanko account takeover via open redirect in SAML login
Only Hanko backends with SAML enabled and a trailing ** wildcard in allowed_redirect_urls are affected; exact-URL-only allowlists are not. Fixed in Hanko 3.2.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.2.0
- Who is exposed
- Specific setups only
Summary
Hanko contains an open redirect flaw in its SAML login redirect check that lets an unauthenticated attacker, remotely and without logging in, bypass the allowlist by appending attacker-controlled domain suffixes to allowed hostnames. By luring a victim to a crafted /saml/auth login link, the attacker can capture the one-time hanko_token and redeem it without PKCE to take over the victim's session.
Written by a model
Original description
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 hanko_token and redeem it without PKCE to hijack the victim's session.
Who should check
Teams running the teamhanko hanko backend v3 (Go) up to 3.1.2 with SAML SSO and ** wildcards in allowed_redirect_urls.
“github.com/teamhanko/hanko/backend/v3”
What to do
Check whether your setup matches what the bug needs.
Hanko backend has SAML enabled with allowed_redirect_urls using a trailing ** wildcard entry (the documented form). Deployments using only exact-URL allowlists are not affected.Upgrade to a fixed version: 3.2.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133705 (Hanko before 3.2.0 Account Takeover via SAML Redirect Allowlist Bypass), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133705 (entry last updated 2026-11-20):
Affected:
- Go package github.com/teamhanko/hanko/backend/v3: fixed in 3.2.0
Fixed versions: 3.2.0.
Conditions (all must be true for the bug to be hit):
- Hanko backend has SAML enabled with allowed_redirect_urls using a trailing ** wildcard entry (the documented form). (source: https://github.com/teamhanko/hanko/security/advisories/GHSA-jfqc-fr2q-fvx6)
- Deployments using only exact-URL allowlists are not affected. (source: https://github.com/teamhanko/hanko/security/advisories/GHSA-jfqc-fr2q-fvx6)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-133705 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133705 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/teamhanko/hanko/security/advisories/GHSA-jfqc-fr2q-fvx6
- https://github.com/teamhanko/hanko/commit/c34e9163df0aa15b6a9cc3a70ff9be01419199b2
- https://github.com/teamhanko/hanko/blob/backend/v3.1.2/backend/config/config_saml.go
- https://github.com/teamhanko/hanko/releases/tag/backend/v3.2.0
- https://www.vulncheck.com/advisories/hanko-before-3.2.0-account-takeover-via-saml-redirect-allowlist-bypass
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133705
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133705"}.Affected versions
cve.now Index
- Exploitation0/40No signal
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach10/20Affects Go packages
- Severity8.6/10CVSS 7.6, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 81 if added to CISA KEV
- Would score about 76 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Evidence 7
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · teamhanko/hanko · Advisory GHSA-jfqc-fr2q-fvx6 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133705 |
| Record | NVD · CVE-2026-133705 |
| Other links 4 | |
| Patch | GitHub · teamhanko/hanko · Commit c34e9163 |
| Repository | GitHub · teamhanko/hanko · v3.1.2/backend/config/config_saml.go |
| Repository | GitHub · teamhanko/hanko · Release backend/v3.2.0 |
| Link | vulncheck.com · advisories/hanko-before-3.2.0-account-takeover-via-saml-redirect-allowlist-bypass |
Questions about CVE-2026-133705
Is CVE-2026-133705 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A flaw in the SAML redirect allowlist lets an attacker capture a one-time hanko_token and redeem it for the victim's full session, taking over SAML SSO accounts. It also gives an open redirect to arbitrary hosts.
Source: github.com
Which versions are affected by CVE-2026-133705?
github.com/teamhanko/hanko/backend/v3 (Go): before 3.2.0.
Source: cve.now feed data
Am I affected, and how do I check?
Hanko versions before 3.2.0 with SAML enabled and a trailing ** wildcard entry in allowed_redirect_urls, the form shown in Hanko's own k8s overlay example. Deployments using only exact-URL allowlists are unaffected. To check, review the allowed_redirect_urls setting in the Hanko backend configuration and the Hanko version in use.
Source: github.com
How do I fix CVE-2026-133705?
Upgrade Hanko to 3.2.0 or later, which is the fixed version listed for this vulnerability.
Source: github.com
Related
- CVE-2026-115082Vulnerability in the Oracle Hyperion Infrastructure Technology product of Oracle Hyperion (component: Installation and Configuration).
- CVE-2026-76007IBM Engineering AI hub Open Redirect
- CVE-2026-91586Vulnerability in the Oracle WebCenter Portal product of Oracle Fusion Middleware (component: Composer).
- CVE-2026-117517Apache Tomcat: Fix for CVE-2026-25854 was incomplete
- CVE-2026-91666Vulnerability in the Oracle WebCenter Content product of Oracle Fusion Middleware (component: Content Server).
- CVE-2026-114998Vulnerability in the Oracle Hyperion Data Relationship Management product of Oracle Hyperion (component: Access and security).
No corrections so far. Something wrong on this page? Report an error.