Vulnerability in goauthentik.io (CVE-2026-47201)
Summary
Vulnerability in goauthentik.io (CVE-2026-47201). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 0.0.0-20260528144335-a370d76d23c7 or later.
Original description
The description as published by the source.
authentik is an open-source identity provider. Prior to versions 2025.12.5, 2026.2.3, and 2026.5.1, authentik's SAML Source ACS endpoint is vulnerable to XML Signature Wrapping when validating upstream SAML responses. An attacker with any account at the upstream IdP can reuse a valid signed assertion to authenticate as another federated user. This issue has been patched in versions 2025.12.5, 2026.2.3, and 2026.5.1.
Source: GitHub Security Advisories (Global) 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-47201 has been found in goauthentik.io.
Successful exploitation can lead to full system takeover. CVSS score: 8.5/10.
What to do: upgrade goauthentik.io to 0.0.0-20260528144335-a370d76d23c7 or later.
If unsure, ask your IT team or search "goauthentik.io CVE-2026-47201" on the vendor's site.
CVE-2026-47201 (goauthentik.io) — CWE-20 / CVSS v3 8.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.0.0-20260528144335-a370d76d23c7 — 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.
A vulnerability (CWE-20) exists in goauthentik.io.
Check the vendor advisory for the affected versions of goauthentik.io.
Severity: High (CVSS 8.5/10). Successful exploitation can lead to full system takeover.
Update to 0.0.0-20260528144335-a370d76d23c7.
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 'goauthentik.io' . 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 'goauthentik.io' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
goauthentik.ioを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade goauthentik.io to 0.0.0-20260528144335-a370d76d23c7ステージング環境で 0.0.0-20260528144335-a370d76d23c7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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
- package github.com
- web github.com
- web github.com