CVE-2025-64708VulnerabilityPublished 19 Nov 2025

CVE-2025-64708: goauthentik authentik · Insufficient Session Expiration

Affects goauthentik authentikSource CVE Database V5

Not known to be exploited · CVSS 5.8 Medium : upgrade to 2025.10.2 or 2025.8.5 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2025.10.2, 2025.8.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Nov 2025
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-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade github.com/goauthentik/authentik to 2025.10.2 or 2025.8.5.

Affected software

Product	Affected	Fixed in
Gogithub.com/goauthentik/authentik`pkg:golang/github.com/goauthentik/authentik`Other threats	Affected <2025.8.5 <2025.10.2	Fixed in 2025.8.5 2025.10.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

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.

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.

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.

CWE-613Insufficient Session Expiration (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."
Implementation
Set sessions/credentials expiration date.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.1 (opens in a new tab)
V2.8.6 (opens in a new tab)
V3.6.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Nov 2025, 17:59 UTC

WeaknessesCWE-613

Technical details

References

Community reviews

Related threats