What’s Vulnerable › Vulnerabilities

CVE-2024-52289: authentik has an insecure default configuration for OAuth2 Redirect URIs

• Severity: critical (CVSS 9.8 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 1.1% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2024-11-21 · updated 2026-06-17
• Weakness: CWE-185

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 `\.`.

Affected products

• goauthentik authentik: before 2024.8.5; from 2024.10.0 before 2024.10.3 — fixed in 2024.10.3, 2024.8.5

How to fix

Upgrade to a fixed version: goauthentik authentik 2024.10.3, 2024.8.5. Check the vendor advisory for mitigations.

References

• https://github.com/goauthentik/authentik/commit/85bb638243c8d7ea42ddd3b15b3f51a90d2b8c54
• https://github.com/goauthentik/authentik/security/advisories/GHSA-3q5w-6m3x-64gj
• https://www.vicarius.io/vsociety/posts/cve-2024-52289-detect-authentik-vulnerability
• https://www.vicarius.io/vsociety/posts/cve-2024-52289-mitigate-authentik-vulnerability

Get alerted when CVE-2024-52289 or the next vulnerability affects your stack