mirror of
https://github.com/goauthentik/authentik
synced 2026-04-27 18:07:15 +02:00
6672e6aaa4
Automated internal backport of patch 1487-invitation-expiry.sec.patch to authentik-main Co-authored-by: authentik-automation[bot] <135050075+authentik-automation[bot]@users.noreply.github.com>
28 lines
1.1 KiB
Markdown
28 lines
1.1 KiB
Markdown
# CVE-2025-64708
|
|
|
|
_Reported by [@melizeche](https://github.com/melizeche)_
|
|
|
|
## Invitation expiry is delayed by at least 5 minutes
|
|
|
|
### 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
|
|
|
|
You 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.
|
|
|
|
```python
|
|
return not context['flow_plan'].context['invitation'].is_expired
|
|
```
|
|
|
|
### For more information
|
|
|
|
If you have any questions or comments about this advisory:
|
|
|
|
- Email us at [security@goauthentik.io](mailto:security@goauthentik.io).
|