CVE-2025-64708: CWE-613: Insufficient Session Expiration in goauthentik authentik
authentik is an open-source Identity Provider. Prior to versions 2025.8.5 and 2025.10.2, in previous authentik versions, invitations were considered valid regardless if they are expired or not, thus relying on background tasks to clean up expired ones. In a normal scenario this can take up to 5 minutes because the cleanup of expired objects is scheduled to run every 5 minutes. However, with a large amount of tasks in the backlog, this might take longer. authentik versions 2025.8.5 and 2025.10.2 fix this issue. A workaround involves creating a policy that explicitly checks whether the invitation is still valid, and then bind it to the invitation stage on the invitation flow, and denying access if the invitation is not valid.
AI Analysis
Technical Summary
CVE-2025-64708 is a vulnerability classified under CWE-613 (Insufficient Session Expiration) affecting the open-source Identity Provider software authentik. In versions prior to 2025.8.5 and 2025.10.2, invitation tokens used for onboarding or access provisioning remain valid until a background cleanup task removes expired invitations. This cleanup task is scheduled to run every 5 minutes, but under heavy load or backlog conditions, expired invitations may persist longer than intended. Consequently, an attacker could exploit this window to use expired invitations to gain unauthorized access to the system. The vulnerability does not require any privileges or user interaction, making it remotely exploitable over the network. The flaw impacts confidentiality by potentially allowing unauthorized access via stale invitations but does not affect integrity or availability. The fixed versions enforce explicit validation of invitation expiration during the invitation flow, eliminating reliance on background cleanup. A practical mitigation before patching is to implement a policy that checks invitation validity explicitly and denies access if the invitation is expired. No known exploits are reported in the wild as of now. This vulnerability highlights the risks of relying solely on asynchronous cleanup tasks for session or token expiration in identity management systems.
Potential Impact
For European organizations, this vulnerability poses a risk of unauthorized access through expired invitation tokens, potentially exposing sensitive identity and access management resources. Since authentik is used as an Identity Provider, exploitation could allow attackers to bypass onboarding controls or gain initial footholds in corporate networks. This can lead to confidentiality breaches, especially in sectors handling sensitive personal data such as finance, healthcare, and government. The medium severity rating reflects that while the impact on integrity and availability is minimal, the confidentiality risk is significant enough to warrant prompt remediation. Organizations with high volumes of invitation workflows or those experiencing heavy system loads may face longer expiration delays, increasing exposure. Additionally, the vulnerability could be leveraged as part of a broader attack chain to escalate privileges or move laterally within networks. Given the critical role of identity providers in access control, exploitation could undermine trust in authentication processes and complicate compliance with GDPR and other data protection regulations.
Mitigation Recommendations
European organizations should immediately upgrade authentik to versions 2025.8.5 or 2025.10.2 where the vulnerability is fixed. Until patching is possible, implement a policy within authentik that explicitly verifies the validity of invitations during the invitation flow and denies access if invitations are expired. Monitor the backlog of cleanup tasks to ensure expired invitations are removed promptly and consider increasing the frequency of cleanup tasks if feasible. Review and tighten invitation issuance policies to minimize the number and lifespan of active invitations. Conduct audits of invitation usage logs to detect any anomalous or repeated use of expired tokens. Integrate multi-factor authentication (MFA) in the invitation acceptance process to add an additional layer of security. Educate administrators and users about the risks of invitation misuse and enforce strict controls on invitation distribution. Finally, maintain vigilant monitoring for suspicious access patterns that could indicate exploitation attempts.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Belgium, Italy, Spain
CVE-2025-64708: CWE-613: Insufficient Session Expiration in goauthentik authentik
Description
authentik is an open-source Identity Provider. Prior to versions 2025.8.5 and 2025.10.2, in previous authentik versions, invitations were considered valid regardless if they are expired or not, thus relying on background tasks to clean up expired ones. In a normal scenario this can take up to 5 minutes because the cleanup of expired objects is scheduled to run every 5 minutes. However, with a large amount of tasks in the backlog, this might take longer. authentik versions 2025.8.5 and 2025.10.2 fix this issue. A workaround involves creating a policy that explicitly checks whether the invitation is still valid, and then bind it to the invitation stage on the invitation flow, and denying access if the invitation is not valid.
AI-Powered Analysis
Technical Analysis
CVE-2025-64708 is a vulnerability classified under CWE-613 (Insufficient Session Expiration) affecting the open-source Identity Provider software authentik. In versions prior to 2025.8.5 and 2025.10.2, invitation tokens used for onboarding or access provisioning remain valid until a background cleanup task removes expired invitations. This cleanup task is scheduled to run every 5 minutes, but under heavy load or backlog conditions, expired invitations may persist longer than intended. Consequently, an attacker could exploit this window to use expired invitations to gain unauthorized access to the system. The vulnerability does not require any privileges or user interaction, making it remotely exploitable over the network. The flaw impacts confidentiality by potentially allowing unauthorized access via stale invitations but does not affect integrity or availability. The fixed versions enforce explicit validation of invitation expiration during the invitation flow, eliminating reliance on background cleanup. A practical mitigation before patching is to implement a policy that checks invitation validity explicitly and denies access if the invitation is expired. No known exploits are reported in the wild as of now. This vulnerability highlights the risks of relying solely on asynchronous cleanup tasks for session or token expiration in identity management systems.
Potential Impact
For European organizations, this vulnerability poses a risk of unauthorized access through expired invitation tokens, potentially exposing sensitive identity and access management resources. Since authentik is used as an Identity Provider, exploitation could allow attackers to bypass onboarding controls or gain initial footholds in corporate networks. This can lead to confidentiality breaches, especially in sectors handling sensitive personal data such as finance, healthcare, and government. The medium severity rating reflects that while the impact on integrity and availability is minimal, the confidentiality risk is significant enough to warrant prompt remediation. Organizations with high volumes of invitation workflows or those experiencing heavy system loads may face longer expiration delays, increasing exposure. Additionally, the vulnerability could be leveraged as part of a broader attack chain to escalate privileges or move laterally within networks. Given the critical role of identity providers in access control, exploitation could undermine trust in authentication processes and complicate compliance with GDPR and other data protection regulations.
Mitigation Recommendations
European organizations should immediately upgrade authentik to versions 2025.8.5 or 2025.10.2 where the vulnerability is fixed. Until patching is possible, implement a policy within authentik that explicitly verifies the validity of invitations during the invitation flow and denies access if invitations are expired. Monitor the backlog of cleanup tasks to ensure expired invitations are removed promptly and consider increasing the frequency of cleanup tasks if feasible. Review and tighten invitation issuance policies to minimize the number and lifespan of active invitations. Conduct audits of invitation usage logs to detect any anomalous or repeated use of expired tokens. Integrate multi-factor authentication (MFA) in the invitation acceptance process to add an additional layer of security. Educate administrators and users about the risks of invitation misuse and enforce strict controls on invitation distribution. Finally, maintain vigilant monitoring for suspicious access patterns that could indicate exploitation attempts.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2025-11-10T14:07:42.921Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 691dfb7693c808727dc04388
Added to database: 11/19/2025, 5:16:38 PM
Last enriched: 11/26/2025, 5:59:15 PM
Last updated: 1/7/2026, 5:44:03 AM
Views: 73
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-2025-14835: CWE-80 Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) in opajaap WP Photo Album Plus
HighCVE-2026-0650: CWE-306 Missing Authentication for Critical Function in OpenFlagr Flagr
CriticalCVE-2025-15474: CWE-770 Allocation of Resources Without Limits or Throttling in AuntyFey AuntyFey Smart Combination Lock
MediumCVE-2025-14468: CWE-352 Cross-Site Request Forgery (CSRF) in mohammed_kaludi AMP for WP – Accelerated Mobile Pages
MediumCVE-2025-9611: CWE-749 Exposed Dangerous Method or Function in Microsoft Playwright
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.