Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
Authentik Fails to Verify IP Address Headers
BIT-authentik-2023-36456
CVE-2023-36456
GHSA-cmxp-jcw7-jjjv
Summary
Authentik, an open-source Identity Provider, doesn't properly check IP address headers from users behind a reverse proxy. This can lead to fake IP addresses being logged, bypassing security checks, and unreliable user session tracking. To fix this, update to version 2023.4.3 or 2023.5.5.
What to do
- Update authentik to version 2023.5.5.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| Bitnami | – | authentik |
>= 2023.5.0, < 2023.5.5 Fix: upgrade to 2023.5.5
|
Original title
Authentik lacks Proxy IP headers validation
Original description
authentik is an open-source Identity Provider. Prior to versions 2023.4.3 and 2023.5.5, authentik does not verify the source of the X-Forwarded-For and X-Real-IP headers, both in the Python code and the go code. Only authentik setups that are directly accessible by users without a reverse proxy are susceptible to this. Possible spoofing of IP addresses in logs, downstream applications proxied by (built in) outpost, IP bypassing in custom flows if used.
This poses a possible security risk when someone has flows or policies that check the user's IP address, e.g. when they want to ignore the user's 2 factor authentication when the user is connected to the company network. A second security risk is that the IP addresses in the logfiles and user sessions are not reliable anymore. Anybody can spoof this address and one cannot verify that the user has logged in from the IP address that is in their account's log. A third risk is that this header is passed on to the proxied application behind an outpost. The application may do any kind of verification, logging, blocking or rate limiting based on the IP address, and this IP address can be overridden by anybody that want to.
Versions 2023.4.3 and 2023.5.5 contain a patch for this issue.
This poses a possible security risk when someone has flows or policies that check the user's IP address, e.g. when they want to ignore the user's 2 factor authentication when the user is connected to the company network. A second security risk is that the IP addresses in the logfiles and user sessions are not reliable anymore. Anybody can spoof this address and one cannot verify that the user has logged in from the IP address that is in their account's log. A third risk is that this header is passed on to the proxied application behind an outpost. The application may do any kind of verification, logging, blocking or rate limiting based on the IP address, and this IP address can be overridden by anybody that want to.
Versions 2023.4.3 and 2023.5.5 contain a patch for this issue.
- https://github.com/goauthentik/authentik/commit/15026748d19d490eb2baf9a9566ead4f... URL
- https://github.com/goauthentik/authentik/commit/c07a48a3eccbd7b23026f72136d3392b... URL
- https://github.com/goauthentik/authentik/security/advisories/GHSA-cmxp-jcw7-jjjv URL
- https://goauthentik.io/docs/releases/2023.4#fixed-in-202343 URL
- https://goauthentik.io/docs/releases/2023.5#fixed-in-202355 URL
- https://nvd.nist.gov/vuln/detail/CVE-2023-36456 URL
Published: 16 Apr 2026 · Updated: 17 Apr 2026 · First seen: 17 Apr 2026