{"id":"CVE-2024-52289","aliases":["BIT-authentik-2024-52289","EUVD-2024-45991","GHSA-3q5w-6m3x-64gj"],"status":"published","title":"authentik has an insecure default configuration for OAuth2 Redirect URIs","description":"authentik is an open-source identity provider. Redirect URIs in the OAuth2 provider in authentik are checked by RegEx comparison.\nWhen 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 `\\.`.","severity":{"version":"4.0","score":7.9,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-08","score":0.01091,"percentile":0.65605,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-185"],"published":"2024-11-21T17:18:41Z","modified":"2026-10-28T02:30:57Z","fixes":[{"ecosystem":"Bitnami","package":"authentik","fixed_in":["2024.8.5","2024.10.3"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Bitnami","package":"authentik","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2024.8.5"},{"introduced":"2024.10.0"},{"fixed":"2024.10.3"}]}]}],"products":[{"vendor":"goauthentik","product":"authentik"}],"references":[{"url":"https://github.com/goauthentik/authentik/security/advisories/GHSA-3q5w-6m3x-64gj","tags":["x_refsource_CONFIRM","Vendor Advisory","advisory"]},{"url":"https://github.com/goauthentik/authentik/commit/85bb638243c8d7ea42ddd3b15b3f51a90d2b8c54","tags":["x_refsource_MISC","Patch","fix"]},{"url":"https://www.vicarius.io/vsociety/posts/cve-2024-52289-detect-authentik-vulnerability","tags":["web"]},{"url":"https://www.vicarius.io/vsociety/posts/cve-2024-52289-mitigate-authentik-vulnerability","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-52289","tags":["web","advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/52xxx/CVE-2024-52289.json","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2024-52289","title":"authentik has an insecure default configuration for OAuth2 Redirect URIs","description":"authentik is an open-source identity provider. Redirect URIs in the OAuth2 provider in authentik are checked by RegEx comparison.\nWhen 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 `\\.`.","status":"published","published":"2024-11-21T17:18:41.161Z","modified":"2025-09-23T18:21:58.9Z","cvss":[{"version":"4.0","score":7.9,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H","level":"high","assessor":"cna"}],"cwes":["CWE-185"],"updated_at":"2026-11-02T14:34:03.661584Z"}],"euvd":[{"id":"EUVD-2024-45991","description":"authentik is an open-source identity provider. Redirect URIs in the OAuth2 provider in authentik are checked by RegEx comparison.\nWhen 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 `\\.`.","status":"published","published":"2024-11-21T17:18:41Z","modified":"2025-09-23T18:21:58Z","cvss":[{"version":"4.0","score":7.9,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H","level":"high"}],"updated_at":"2026-11-02T20:31:40.470019Z"}],"nvd":[{"id":"CVE-2024-52289","description":"authentik is an open-source identity provider. Redirect URIs in the OAuth2 provider in authentik are checked by RegEx comparison.\nWhen 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 `\\.`.","status":"published","published":"2024-11-21T18:15:12.06Z","modified":"2026-06-17T08:06:56.863Z","cvss":[{"version":"4.0","score":7.9,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"high","assessor":"secondary"},{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical","assessor":"primary"}],"cwes":["CWE-185"],"updated_at":"2026-11-02T14:10:37.996328Z"}],"osv":[{"id":"CVE-2024-52289","title":"authentik has an insecure default configuration for OAuth2 Redirect URIs","description":"authentik is an open-source identity provider. Redirect URIs in the OAuth2 provider in authentik are checked by RegEx comparison.\nWhen 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 `\\.`.","status":"published","published":"2024-11-21T17:18:41.161Z","modified":"2026-10-28T02:30:57.718982283Z","cvss":[{"version":"4.0","score":7.9,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H","level":"high"}],"cwes":["CWE-185"],"updated_at":"2026-11-02T15:44:44.032344Z"},{"id":"BIT-authentik-2024-52289","title":"authentik has an insecure default configuration for OAuth2 Redirect URIs","description":"authentik is an open-source identity provider. Redirect URIs in the OAuth2 provider in authentik are checked by RegEx comparison.\nWhen 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 `\\.`.","status":"published","published":"2026-04-16T23:36:22.514Z","modified":"2026-09-10T16:01:08.826876098Z","updated_at":"2026-11-02T15:28:28.70813Z"}]}}