# CVE-2026-49448: authentik: SourceStage bypass via empty POST

> Attackers can bypass the Source stage in authentik by sending an empty POST request, potentially circumventing authentication controls.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Jun 2026
- **Updated:** 3 Jun 2026
- **Also known as:** BIT-authentik-2026-49448, GHSA-xp7f-xjjx-gwm8

## What is CVE-2026-49448?

CVE-2026-49448 is a critical authentication bypass vulnerability in goauthentik authentik, published on 2 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

authentik is an open-source identity provider. Prior to versions 2025.12.6, 2026.2.4, and 2026.5.1, the Source stage can be bypassed by sending an empty POST. This issue has been patched in versions 2025.12.6, 2026.2.4, and 2026.5.1.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-49448?

1 open source package ship an affected version, including authentik. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `authentik` | Bitnami | All versions | 2025.12.6, 2026.2.4, 2026.5.1 |

Products: Goauthentik Authentik.

## How do I fix CVE-2026-49448?

Upgrade authentik to a fixed version for your release line: 2025.12.6, 2026.2.4 or 2026.5.1.

## Is CVE-2026-49448 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49448 exists.

## Other vulnerabilities in goauthentik authentik

- [CVE-2023-46249](https://insights.sbomify.com/CVE-2023-46249/): authentik potential installation takeover when default admin user is deleted (critical 9.7)
- [CVE-2022-23555](https://insights.sbomify.com/CVE-2022-23555/): authentik vulnerable to Improper Authentication via invitation URL token reuse (critical 9.4)
- [CVE-2026-42849](https://insights.sbomify.com/CVE-2026-42849/): authentik: Reflected XSS in SFE AutosubmitStage allows IDP account takeover (critical 9.3)
- [CVE-2026-25227](https://insights.sbomify.com/CVE-2026-25227/): authentik affected by Remote Code Execution via Context Key Injection in PropertyMapping Test Endpoint (critical 9.1)
- [CVE-2024-47070](https://insights.sbomify.com/CVE-2024-47070/): authentik vulnerable to password authentication bypass via X-Forwarded-For HTTP header (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49448 and fix it if it is affected.

What it is: CVE-2026-49448 is a critical authentication bypass vulnerability in goauthentik authentik, published on 2 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49448 exists.

Affected packages and fixed versions:
- authentik (Bitnami): affected all versions; fixed in 2025.12.6, 2026.2.4, 2026.5.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-49448/ (Markdown: https://insights.sbomify.com/CVE-2026-49448/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49448
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49448
- OSV: https://osv.dev/vulnerability/CVE-2026-49448

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-49448/
Summaries are generated and may contain mistakes; the official description above is the record.