CVE-2025-64708
published 2025-11-19CVE-2025-64708: 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…
PriorityP429medium5.3CVSS 3.1
AVNACLPRNUINSUCLINAN
EPSS
0.22%
12.0th percentile
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.
Affected
4 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| goauthentik | authentik | < 2025.10.2 | 2025.10.2 |
| goauthentik | authentik | < 2025.8.5 | 2025.8.5 |
| goauthentik | authentik | >= 2025.10.0 < 2025.10.2 | 2025.10.2 |
| goauthentik | authentik | >= 2025.8.0 < 2025.8.5 | 2025.8.5 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
authentik's invitation expiry is delayed by at least 5 minutes in goauthentik.io
osv·2025-12-15
CVE-2025-64708 authentik's invitation expiry is delayed by at least 5 minutes in goauthentik.io
authentik's invitation expiry is delayed by at least 5 minutes in goauthentik.io
authentik's invitation expiry is delayed by at least 5 minutes in goauthentik.io.
NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.
(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)
The additional affected modules and versions are: goauthentik.io before v0.0.0-20251119135424-6672e6aaa41e.
OSV
authentik's invitation expiry is delayed by at least 5 minutes
osv·2025-11-19
CVE-2025-64708 [MEDIUM] authentik's invitation expiry is delayed by at least 5 minutes
authentik's 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
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.
```python
return
GHSA
authentik's invitation expiry is delayed by at least 5 minutes
ghsa·2025-11-19
CVE-2025-64708 [MEDIUM] CWE-613 authentik's invitation expiry is delayed by at least 5 minutes
authentik's 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
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.
```python
return
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2025-11-19
Published