Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
7.9
Authentik's OAuth Redirect URI Checks Can Be Bypassed
CVE-2024-52289
BIT-authentik-2024-52289
Summary
Authentik's open-source identity provider has a flaw in its OAuth2 redirect URI checks. If a provider is not configured with any redirect URIs, an attacker can register a domain that resembles a valid one, potentially allowing unauthorized access. To fix this, update to a patched version or ensure wildcard characters are escaped in the redirect URI configuration.
What to do
- Update authentik to version 2024.10.3.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| – | goauthentik | authentik |
< 2024.8.5 >= 2024.10.0, < 2024.10.3 cpe:2.3:a:goauthentik:authentik:*:*:*:*:*:*:*:* |
| Bitnami | – | authentik |
>= 2024.10.0, < 2024.10.3 Fix: upgrade to 2024.10.3
|
Original title
authentik has an insecure default configuration for OAuth2 Redirect URIs
Original description
authentik is an open-source identity provider. Redirect URIs in the OAuth2 provider in authentik are checked by RegEx comparison.
When no Redirect URIs are configured in a provider, authentik will automatically use the first redirect_uri value received as an allowed redirect URI, without escaping characters that have a special meaning in RegEx. Similarly, the documentation did not take this into consideration either. Given a provider with the Redirect URIs set to https://foo.example.com, an attacker can register a domain fooaexample.com, and it will correctly pass validation. authentik 2024.8.5 and 2024.10.3 fix this issue. As a workaround, When configuring OAuth2 providers, make sure to escape any wildcard characters that are not intended to function as a wildcard, for example replace `.` with `\.`.
When no Redirect URIs are configured in a provider, authentik will automatically use the first redirect_uri value received as an allowed redirect URI, without escaping characters that have a special meaning in RegEx. Similarly, the documentation did not take this into consideration either. Given a provider with the Redirect URIs set to https://foo.example.com, an attacker can register a domain fooaexample.com, and it will correctly pass validation. authentik 2024.8.5 and 2024.10.3 fix this issue. As a workaround, When configuring OAuth2 providers, make sure to escape any wildcard characters that are not intended to function as a wildcard, for example replace `.` with `\.`.
nvd CVSS3.1
9.8
nvd CVSS4.0
7.9
Vulnerability type
CWE-185
- https://github.com/goauthentik/authentik/commit/85bb638243c8d7ea42ddd3b15b3f51a9... Patch
- https://github.com/goauthentik/authentik/security/advisories/GHSA-3q5w-6m3x-64gj Vendor Advisory
- https://www.vicarius.io/vsociety/posts/cve-2024-52289-detect-authentik-vulnerabi...
- https://www.vicarius.io/vsociety/posts/cve-2024-52289-mitigate-authentik-vulnera...
- https://nvd.nist.gov/vuln/detail/CVE-2024-52289 URL
Published: 16 Apr 2026 · Updated: 17 Apr 2026 · First seen: 7 Mar 2026