Vulnerability in goauthentik.io (CVE-2025-64521)
Summary
Vulnerability in goauthentik.io (CVE-2025-64521). Risk of unauthorized operations or information disclosure. Exploitable via client_id. Mitigation: upgrade to 0.0.0-20251119140106-9dbdfc3f1be0 or later.
Original description
The description as published by the source.
authentik is an open-source Identity Provider. Prior to versions 2025.8.5 and 2025.10.2, when authenticating with client_id and client_secret to an OAuth provider, authentik creates a service account for the provider. In previous authentik versions, authentication for this account was possible even when the account was deactivated. Other permissions are correctly applied and federation with other providers still take assigned policies correctly into account. authentik versions 2025.8.5 and 2025.10.2 fix this issue. A workaround involves adding a policy to the application that explicitly checks if the service account is still valid, and deny access if not.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-2025-64521 has been found in goauthentik.io.
Attackers can target a specific entry point like client_id over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade goauthentik.io to 0.0.0-20251119140106-9dbdfc3f1be0 or later.
If unsure, ask your IT team or search "goauthentik.io CVE-2025-64521" on the vendor's site.
CVE-2025-64521 (goauthentik.io) — CWE-286
Attack vector: remote (network-reachable)
Attack surface: client_id / client_secret
Patched: 0.0.0-20251119140106-9dbdfc3f1be0 — 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-286) exists in goauthentik.io. Attackers reach the vulnerable code path via client_id.
Check the vendor advisory for the affected versions of goauthentik.io. Attack surface: client_id / client_secret.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.0.0-20251119140106-9dbdfc3f1be0.
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-20251119140106-9dbdfc3f1be0ステージング環境で 0.0.0-20251119140106-9dbdfc3f1be0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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
- patch github.com