Skip to content
Fencer Intel
medium 5.8

CVE-2025-64708 json

authentik invitation expiry is delayed by at least 5 minutes

published 11mo ago modified 22d ago also BIT-authentik-2025-64708 , EUVD-2025-198187 , GHSA-ch7q-53v8-73pc , GO-2025-4136

cvss
5.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 18%
public exploits
0
none known

Summary

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.

Patch / fix

  • go goauthentik.io 0.0.0-20251119135424-6672e6aaa41e
  • bitnami authentik 0.0.0-20251119135424-6672e6aaa41e, 2025.8.5, 2025.10.2
  • goauthentik authentik 0.0.0-20251119135424-6672e6aaa41e, 2025.8.5, 2025.10.2
  • govulncheck-vulndb openSUSE Leap 15.6 0.0.20251230T014957-150000.1.134.1

suse advisories SUSE-SU-2026:0037-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

Is CVE-2025-64708 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
11mo ago

Exploit prediction

0.27% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
GitHub 3.1 5.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OSV 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
go goauthentik.io
<0.0.0-20251119135424-6672e6aaa41e
all versions
0.0.0-20251119135424-6672e6aaa41e
bitnami authentik
<0.0.0-20251119135424-6672e6aaa41e
>=2000.0.0, <2025.8.5
>=2025.9.0, <2025.10.2
0.0.0-20251119135424-6672e6aaa41e
2025.8.5
2025.10.2

Affected products

  • goauthentik authentik

Classification

Weakness
  • CWE-613 DEPRECATED: Insufficient Session Expiration

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.