Servers and applications
GHSA-5wcc-hf24-rf5h
Unauthenticated Access via Client-Controlled X-Original-URI Header in Nginx Forward-Auth Mode
- Severity
- High 8.7
- 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 · Only under certain conditions · No login needed · No user action needed
- Attacker can
- Read data · Change data
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N- Sources
- Project advisories (GitHub)
Description
In nginx forward-auth mode, the authentik outpost reads the forwarded request URL from a header that nginx does not set, but that a client can freely inject. By crafting this header to point at an internal outpost path, an unauthenticated attacker can cause the outpost to return HTTP 200 — causing nginx to forward the original request to the protected backend without authentication.
This vulnerability only affects deployments using authentik's nginx forward-auth integration. Traefik, Caddy, and proxy mode deployments are not affected.
In nginx forward-auth mode, the outpost builds the URL it evaluates from a header that nginx never sets but clients can freely inject. Because nginx's auth_request module forwards all client headers to the authentication subrequest, an attacker-supplied value reaches the outpost unmodified.
The outpost unconditionally allows requests whose forwarded URL path begins with /outpost.goauthentik.io/ (to permit internal endpoints such as the OAuth…
Workarounds
Operators can mitigate this immediately at the nginx layer by explicitly clearing the X-Original-URI header in the nginx location block that proxies traffic to the outpost. This prevents the attacker-supplied value from reaching the outpost regardless of the application-level logic. Refer to the nginx documentation for proxy_set_header to clear individual headers.
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-5wcc-hf24-rf5h
- github.com https://github.com/goauthentik/authentik/security/advisories/GHSA-5wcc-hf24-rf5h