Summary
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.
Workarounds
Users can create a policy that explicitly checks whether the invitation is still valid, and then bind it to the invitation stage on your invitation flow, and deny access if the invitation is not valid.
return not context['flow_plan'].context['invitation'].is_expired
For more information
If users have any questions or comments about this advisory:
- Email the authentik team at [email protected].
Impact
CVE-2025-64708 has a CVSS score of 5.8 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.0.0-20251119135424-6672e6aaa41e); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
authentik 2025.8.5 and 2025.10.2 fix this issue; for other versions the workaround below can be used.
Frequently Asked Questions
- What is CVE-2025-64708? CVE-2025-64708 is a medium-severity security vulnerability in goauthentik.io (go), affecting versions < 0.0.0-20251119135424-6672e6aaa41e. It is fixed in 0.0.0-20251119135424-6672e6aaa41e.
- How severe is CVE-2025-64708? CVE-2025-64708 has a CVSS score of 5.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of goauthentik.io are affected by CVE-2025-64708? goauthentik.io (go) versions < 0.0.0-20251119135424-6672e6aaa41e is affected.
- Is there a fix for CVE-2025-64708? Yes. CVE-2025-64708 is fixed in 0.0.0-20251119135424-6672e6aaa41e. Upgrade to this version or later.
- Is CVE-2025-64708 exploitable, and should I be worried? Whether CVE-2025-64708 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-64708 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-64708? Upgrade
goauthentik.ioto 0.0.0-20251119135424-6672e6aaa41e or later.