Servers and applications
GHSA-3wf5-rj6w-7527
OAuth2 Redirect URI Poisoning via Auto-Save on Unconfigured Provider
- Severity
- High 7.4
- Published
- 12 May 2026
- Last changed
- 12 May 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 2025.12.5, 2026.2.3
- Attack
- Over the network · No login needed · Needs someone to click or open something
- Attacker can
- Read data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N- Sources
- Project advisories (GitHub)
Description
When an OAuth2/OpenID Connect provider has no redirect URIs configured, the first authorization request permanently saves the attacker-supplied redirect_uri into the provider's configuration. This check runs in pre_permission_check() which executes BEFORE authentication, meaning an unauthenticated attacker can poison the provider's redirect URI. All subsequent legitimate OAuth2 flows for that provider will validate against the attacker's URI, enabling authorization code interception.
- Authorization code theft: All OAuth2 authorization codes for the poisoned provider are redirected to the attacker
- Account takeover: Captured authorization codes can be exchanged for access tokens, granting full access to user accounts on relying applications
- Silent persistence: The poisoned redirect URI persists in the database until an admin manually checks and corrects the provider configuration
- Scope: Changed scope (S:C) because the vulnerability in the identity provider compromises security…
Affected software
| Software | Affected versions |
|---|---|
authentikServers and applications · github:goauthentik/authentik |
|
About authentik
The authentication glue you need.
- Total installations
- 1 millionauthentik
- GitHub stars
- 26,351GitHub, 15 Nov 2026
- Forks
- 2,134GitHub, 15 Nov 2026
- Latest release
- version/2026.8.5GitHub, 15 Nov 2026
- Released
- 21 Oct 2026GitHub
- First published on GitHub
- 30 Dec 2019GitHub
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 2026.8 | 2026.8.5 | Yes |
| 2026.5 | 2026.5.8 | Yes |
| 2026.2 | 2026.2.7 | Ended 18 Aug 2026 |
| 2025.12 | 2025.12.6 | Ended 22 May 2026 |
| 2025.10 | 2025.10.4 | Ended 24 Feb 2026 |
| 2025.8 | 2025.8.6 | Ended 13 Jan 2026 |
From endoflife.date.
Vulnerabilities in authentik
- In our list
- 48
- Published in the last 12 months
- 24
- Critical, last 12 months
- 3
- High, last 12 months
- 17
- Known exploited
- 0
- CVE-2026-94613Denial of Service via Malformed SAML MessagesHigh 7.5 9 Sept 2026
- CVE-2026-94611Certain stored credentials readable with view permission aloneHigh 8.1 9 Sept 2026
- CVE-2026-94612Authentication bypass in SAML Sources via assertion confusion and replayHigh 7.4 9 Sept 2026
- CVE-2026-94609Privilege escalation via delegated group and user managementHigh 8.8 9 Sept 2026
- CVE-2026-94606MFA bypass via recipient override in the email authenticatorHigh 8.9 9 Sept 2026
- GHSA-hmrg-vpp4-gj88Broken access control in Shared Signals Framework stream managementMedium 5.4 15 Jul 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-3wf5-rj6w-7527
- github.com https://github.com/goauthentik/authentik/security/advisories/GHSA-3wf5-rj6w-7527