Authentication Bypass in authentik (CVE-2026-49448)
Summary
Authentication bypass in authentik (CVE-2026-49448). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2025.12.6, 2026.2.4, 2026.5.1 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-49448 has been found in authentik.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade authentik to 2025.12.6, 2026.2.4, 2026.5.1 or later.
If unsure, ask your IT team or search "authentik CVE-2026-49448" on the vendor's site.
CVE-2026-49448 (authentik) — CWE-287 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2025.12.6, 2026.2.4, 2026.5.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Authentication bypass (CWE-287) exists in authentik.
Check the vendor advisory for the affected versions of authentik.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 2025.12.6, 2026.2.4, 2026.5.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'authentik' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'authentik' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
authentikを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade authentik to 2025.12.6, 2026.2.4, 2026.5.1ステージング環境で 2025.12.6, 2026.2.4, 2026.5.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com