CVE-2026-25922: goauthentik authentik · Improper Authentication
Affects goauthentik authentikSource CVE Database V5
Not known to be exploited · CVSS 8.8 High · fixed in 2025.12.4 : patch goauthentik authentik soon.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2025.12.4, 2025.10.4, 2025.8.6
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade goauthentik authentik to 2025.12.4, 2025.10.4 or 2025.8.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| goauthentikauthentik | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2026-25922, organizations should immediately upgrade authentik to versions 2025.8.6, 2025.10.4, or 2025.12.4 or later, where the vulnerability is fixed. Review and audit SAML Source configurations to ensure that both 'Verify Assertion Signature' and 'Verify Response Signature' options are enabled, and that the 'Encryption Certificate' setting under Advanced Protocol settings is properly configured. Implement strict validation of SAML assertions and responses to prevent injection of unauthorized assertions. Employ network segmentation and access controls to limit exposure of authentik services to trusted networks and users. Monitor authentication logs for unusual assertion patterns or repeated authentication failures that may indicate exploitation attempts. Consider deploying Web Application Firewalls (WAFs) with rules targeting malformed or suspicious SAML traffic. Conduct regular security assessments and penetration tests focusing on identity provider configurations. Educate administrators on secure SAML configuration best practices to avoid misconfigurations that enable such vulnerabilities. Maintain an incident response plan tailored to identity provider compromises.
Description
authentik is an open-source identity provider. Prior to 2025.8.6, 2025.10.4, and 2025.12.4, when using a SAML Source that has the option Verify Assertion Signature under Verification Certificate enabled and not Verify Response Signature, or does not have the Encryption Certificate setting under Advanced Protocol settings configured, it was possible for an attacker to inject a malicious assertion before the signed assertion that authentik would use instead.authentik 2025.8.6, 2025.10.4, and 2025.12.4 fix this issue.
References
- github.com/goauthentik/authentik/security/advisories/GHSA-jh35-c4cc-wjm4 (opens in a new tab)
- github.com/goauthentik/authentik/releases/tag/version%2F2025.10.4 (opens in a new tab)
- github.com/goauthentik/authentik/releases/tag/version%2F2025.12.4 (opens in a new tab)
- github.com/goauthentik/authentik/releases/tag/version%2F2025.8.6 (opens in a new tab)