NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2025-64708: authentik's invitation expiry is delayed by at least 5 minutes

mediumCVSS 3.1 5.8GHSA-ch7q-53v8-73pc

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.

Published Nov 19, 2025

Affected packages

goauthentik.io

Ecosystem
Go
Affected
< 0.0.0-20251119135424-6672e6aaa41e
Fixed in
0.0.0-20251119135424-6672e6aaa41e
Check
go list -m goauthentik.io

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

Patches

authentik 2025.8.5 and 2025.10.2 fix this issue; for other versions the workaround below can be used.

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:

Credited to melizeche.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Go vulnerabilities

All Go entries