CVE-2026-25922: CWE-287: Improper Authentication in goauthentik authentik
CVE-2026-25922 is a high-severity improper authentication vulnerability in the open-source identity provider authentik. It affects versions prior to 2025. 8. 6, 2025. 10. 4, and 2025. 12. 4 when using a SAML Source configured to verify only the assertion signature but not the response signature, or lacking encryption certificate settings. An attacker can inject a malicious SAML assertion before the legitimate signed assertion, causing authentik to accept the malicious assertion and bypass authentication controls. This vulnerability impacts confidentiality, integrity, and availability, allowing potential unauthorized access without user interaction and with low attack complexity.
AI Analysis
Technical Summary
The vulnerability identified as CVE-2026-25922 affects the open-source identity provider authentik, specifically in its handling of SAML authentication assertions. In versions prior to 2025.8.6, 2025.10.4, and 2025.12.4, when a SAML Source is configured to verify only the assertion signature (via the 'Verify Assertion Signature' option) but not the response signature, or when the 'Encryption Certificate' setting under Advanced Protocol settings is not configured, authentik fails to properly validate the authenticity of the entire SAML response. This improper authentication (CWE-287) allows an attacker to inject a malicious SAML assertion before the legitimate signed assertion within the SAML response. Due to the verification logic, authentik mistakenly uses the injected malicious assertion instead of the signed one, effectively bypassing authentication controls. This flaw can lead to unauthorized access, privilege escalation, and compromise of user identity integrity. The vulnerability is exploitable remotely without user interaction and requires only low privileges (PR:L), making it relatively easy to exploit in network-exposed environments. The CVSS 3.1 base score of 8.8 reflects the high impact on confidentiality, integrity, and availability, as well as the ease of exploitation. The issue was addressed in authentik versions 2025.8.6, 2025.10.4, and 2025.12.4 by correcting the SAML assertion verification process and enforcing stricter validation of signatures and encryption certificates.
Potential Impact
For European organizations, this vulnerability poses a significant risk to identity and access management systems that rely on authentik as an identity provider, especially those using SAML for federated authentication. Exploitation could allow attackers to impersonate legitimate users, gain unauthorized access to sensitive systems and data, and potentially move laterally within networks. This threatens the confidentiality of personal and corporate data, the integrity of authentication processes, and the availability of services relying on authentik for access control. Sectors such as finance, healthcare, government, and critical infrastructure that depend on strong identity verification are particularly vulnerable. Given the widespread adoption of open-source IAM solutions in Europe and the increasing use of SAML in enterprise environments, the impact could be broad. Additionally, regulatory frameworks like GDPR impose strict requirements on identity and access controls, so exploitation could lead to compliance violations and financial penalties.
Mitigation Recommendations
Organizations should immediately upgrade authentik to versions 2025.8.6, 2025.10.4, or 2025.12.4 where the vulnerability is fixed. Beyond patching, administrators must audit SAML Source configurations to ensure that both 'Verify Assertion Signature' and 'Verify Response Signature' options are enabled to enforce comprehensive signature validation. The 'Encryption Certificate' setting under Advanced Protocol settings should be properly configured to prevent unsigned or unencrypted assertions from being accepted. Implement strict monitoring and logging of authentication events to detect anomalous SAML assertions or unexpected authentication flows. Employ network segmentation and access controls to limit exposure of authentik instances to untrusted networks. Consider deploying Web Application Firewalls (WAFs) with rules to detect and block malformed or suspicious SAML responses. Finally, conduct regular security assessments and penetration tests focused on identity provider configurations to proactively identify weaknesses.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Belgium, Italy, Spain, Poland
CVE-2026-25922: CWE-287: Improper Authentication in goauthentik authentik
Description
CVE-2026-25922 is a high-severity improper authentication vulnerability in the open-source identity provider authentik. It affects versions prior to 2025. 8. 6, 2025. 10. 4, and 2025. 12. 4 when using a SAML Source configured to verify only the assertion signature but not the response signature, or lacking encryption certificate settings. An attacker can inject a malicious SAML assertion before the legitimate signed assertion, causing authentik to accept the malicious assertion and bypass authentication controls. This vulnerability impacts confidentiality, integrity, and availability, allowing potential unauthorized access without user interaction and with low attack complexity.
AI-Powered Analysis
Technical Analysis
The vulnerability identified as CVE-2026-25922 affects the open-source identity provider authentik, specifically in its handling of SAML authentication assertions. In versions prior to 2025.8.6, 2025.10.4, and 2025.12.4, when a SAML Source is configured to verify only the assertion signature (via the 'Verify Assertion Signature' option) but not the response signature, or when the 'Encryption Certificate' setting under Advanced Protocol settings is not configured, authentik fails to properly validate the authenticity of the entire SAML response. This improper authentication (CWE-287) allows an attacker to inject a malicious SAML assertion before the legitimate signed assertion within the SAML response. Due to the verification logic, authentik mistakenly uses the injected malicious assertion instead of the signed one, effectively bypassing authentication controls. This flaw can lead to unauthorized access, privilege escalation, and compromise of user identity integrity. The vulnerability is exploitable remotely without user interaction and requires only low privileges (PR:L), making it relatively easy to exploit in network-exposed environments. The CVSS 3.1 base score of 8.8 reflects the high impact on confidentiality, integrity, and availability, as well as the ease of exploitation. The issue was addressed in authentik versions 2025.8.6, 2025.10.4, and 2025.12.4 by correcting the SAML assertion verification process and enforcing stricter validation of signatures and encryption certificates.
Potential Impact
For European organizations, this vulnerability poses a significant risk to identity and access management systems that rely on authentik as an identity provider, especially those using SAML for federated authentication. Exploitation could allow attackers to impersonate legitimate users, gain unauthorized access to sensitive systems and data, and potentially move laterally within networks. This threatens the confidentiality of personal and corporate data, the integrity of authentication processes, and the availability of services relying on authentik for access control. Sectors such as finance, healthcare, government, and critical infrastructure that depend on strong identity verification are particularly vulnerable. Given the widespread adoption of open-source IAM solutions in Europe and the increasing use of SAML in enterprise environments, the impact could be broad. Additionally, regulatory frameworks like GDPR impose strict requirements on identity and access controls, so exploitation could lead to compliance violations and financial penalties.
Mitigation Recommendations
Organizations should immediately upgrade authentik to versions 2025.8.6, 2025.10.4, or 2025.12.4 where the vulnerability is fixed. Beyond patching, administrators must audit SAML Source configurations to ensure that both 'Verify Assertion Signature' and 'Verify Response Signature' options are enabled to enforce comprehensive signature validation. The 'Encryption Certificate' setting under Advanced Protocol settings should be properly configured to prevent unsigned or unencrypted assertions from being accepted. Implement strict monitoring and logging of authentication events to detect anomalous SAML assertions or unexpected authentication flows. Employ network segmentation and access controls to limit exposure of authentik instances to untrusted networks. Consider deploying Web Application Firewalls (WAFs) with rules to detect and block malformed or suspicious SAML responses. Finally, conduct regular security assessments and penetration tests focused on identity provider configurations to proactively identify weaknesses.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-02-09T16:22:17.785Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 698e2eb9c9e1ff5ad808ac35
Added to database: 2/12/2026, 7:49:13 PM
Last enriched: 2/12/2026, 8:03:39 PM
Last updated: 2/12/2026, 8:56:26 PM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-26005: CWE-918: Server-Side Request Forgery (SSRF) in MacWarrior clipbucket-v5
MediumCVE-2026-26000: CWE-1021: Improper Restriction of Rendered UI Layers or Frames in xwiki xwiki-platform
MediumCVE-2026-0619: CWE-190 Integer Overflow or Wraparound in silabs.com Silicon Labs Matter
MediumCVE-2026-25933: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in arduino arduino-app-lab
MediumCVE-2026-25768: CWE-862: Missing Authorization in cloudamqp lavinmq
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.