CVE-2026-25227: CWE-94: Improper Control of Generation of Code ('Code Injection') in goauthentik authentik
authentik is an open-source identity provider. From 2021.3.1 to before 2025.8.6, 2025.10.4, and 2025.12.4, when using delegated permissions, a User that has the permission Can view * Property Mapping or Can view Expression Policy is able to execute arbitrary code within the authentik server container through the test endpoint, which is intended to preview how a property mapping/policy works. authentik 2025.8.6, 2025.10.4, and 2025.12.4 fix this issue.
AI Analysis
Technical Summary
CVE-2026-25227 is a critical vulnerability classified under CWE-94 (Improper Control of Generation of Code), specifically a code injection flaw in the authentik open-source identity provider software. The flaw exists in the test endpoint functionality used to preview property mappings or expression policies. When a user with delegated permissions 'Can view * Property Mapping' or 'Can view Expression Policy' accesses this endpoint, they can inject and execute arbitrary code within the authentik server container. This vulnerability affects multiple versions of authentik starting from 2021.3.1 up to versions before 2025.8.6, 2025.10.4, and 2025.12.4, with fixed releases addressing the issue. The vulnerability requires the attacker to have high-level delegated permissions but does not require user interaction, making it a direct and potent threat. Exploitation can lead to full compromise of the authentik server environment, impacting confidentiality, integrity, and availability of identity management services. The vulnerability has a CVSS v3.1 score of 9.1, indicating critical severity, with network attack vector, low attack complexity, high privileges required, no user interaction, and scope change. No public exploits are currently known, but the potential impact is severe given the role of authentik in identity and access management.
Potential Impact
The impact of CVE-2026-25227 is severe for organizations using authentik as their identity provider. Successful exploitation allows an attacker with delegated permissions to execute arbitrary code on the authentik server container, potentially leading to full system compromise. This can result in unauthorized access to sensitive identity data, manipulation or bypass of authentication and authorization controls, and disruption or denial of identity services. Since authentik often integrates with critical enterprise systems for single sign-on and identity federation, the compromise can cascade to other connected systems, amplifying the damage. The vulnerability threatens confidentiality by exposing sensitive user and configuration data, integrity by allowing unauthorized code execution and policy manipulation, and availability by potentially disrupting identity services. Organizations relying on authentik for identity management face risks of data breaches, privilege escalation, and operational outages if this vulnerability is exploited.
Mitigation Recommendations
To mitigate CVE-2026-25227, organizations should immediately upgrade authentik to one of the fixed versions: 2025.8.6, 2025.10.4, or 2025.12.4. If immediate patching is not feasible, restrict access to the test endpoint to only fully trusted administrators and audit delegated permissions to ensure only necessary users have 'Can view * Property Mapping' or 'Can view Expression Policy' permissions. Implement network segmentation and firewall rules to limit access to the authentik server, especially the test endpoint. Monitor authentik logs for unusual activity related to property mapping or expression policy previews. Employ runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to detect and block suspicious code injection attempts targeting the test endpoint. Regularly review and tighten delegated permission assignments to minimize the number of users with high privileges. Conduct penetration testing focused on the test endpoint to verify the effectiveness of mitigations. Finally, maintain an incident response plan to quickly address any suspected exploitation.
Affected Countries
United States, Germany, United Kingdom, France, Canada, Australia, Netherlands, Sweden, Japan, South Korea
CVE-2026-25227: CWE-94: Improper Control of Generation of Code ('Code Injection') in goauthentik authentik
Description
authentik is an open-source identity provider. From 2021.3.1 to before 2025.8.6, 2025.10.4, and 2025.12.4, when using delegated permissions, a User that has the permission Can view * Property Mapping or Can view Expression Policy is able to execute arbitrary code within the authentik server container through the test endpoint, which is intended to preview how a property mapping/policy works. authentik 2025.8.6, 2025.10.4, and 2025.12.4 fix this issue.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-25227 is a critical vulnerability classified under CWE-94 (Improper Control of Generation of Code), specifically a code injection flaw in the authentik open-source identity provider software. The flaw exists in the test endpoint functionality used to preview property mappings or expression policies. When a user with delegated permissions 'Can view * Property Mapping' or 'Can view Expression Policy' accesses this endpoint, they can inject and execute arbitrary code within the authentik server container. This vulnerability affects multiple versions of authentik starting from 2021.3.1 up to versions before 2025.8.6, 2025.10.4, and 2025.12.4, with fixed releases addressing the issue. The vulnerability requires the attacker to have high-level delegated permissions but does not require user interaction, making it a direct and potent threat. Exploitation can lead to full compromise of the authentik server environment, impacting confidentiality, integrity, and availability of identity management services. The vulnerability has a CVSS v3.1 score of 9.1, indicating critical severity, with network attack vector, low attack complexity, high privileges required, no user interaction, and scope change. No public exploits are currently known, but the potential impact is severe given the role of authentik in identity and access management.
Potential Impact
The impact of CVE-2026-25227 is severe for organizations using authentik as their identity provider. Successful exploitation allows an attacker with delegated permissions to execute arbitrary code on the authentik server container, potentially leading to full system compromise. This can result in unauthorized access to sensitive identity data, manipulation or bypass of authentication and authorization controls, and disruption or denial of identity services. Since authentik often integrates with critical enterprise systems for single sign-on and identity federation, the compromise can cascade to other connected systems, amplifying the damage. The vulnerability threatens confidentiality by exposing sensitive user and configuration data, integrity by allowing unauthorized code execution and policy manipulation, and availability by potentially disrupting identity services. Organizations relying on authentik for identity management face risks of data breaches, privilege escalation, and operational outages if this vulnerability is exploited.
Mitigation Recommendations
To mitigate CVE-2026-25227, organizations should immediately upgrade authentik to one of the fixed versions: 2025.8.6, 2025.10.4, or 2025.12.4. If immediate patching is not feasible, restrict access to the test endpoint to only fully trusted administrators and audit delegated permissions to ensure only necessary users have 'Can view * Property Mapping' or 'Can view Expression Policy' permissions. Implement network segmentation and firewall rules to limit access to the authentik server, especially the test endpoint. Monitor authentik logs for unusual activity related to property mapping or expression policy previews. Employ runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to detect and block suspicious code injection attempts targeting the test endpoint. Regularly review and tighten delegated permission assignments to minimize the number of users with high privileges. Conduct penetration testing focused on the test endpoint to verify the effectiveness of mitigations. Finally, maintain an incident response plan to quickly address any suspected exploitation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-01-30T14:44:47.327Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 698e2eb9c9e1ff5ad808ac29
Added to database: 2/12/2026, 7:49:13 PM
Last enriched: 2/20/2026, 8:22:49 AM
Last updated: 3/30/2026, 2:09:30 AM
Views: 290
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.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.