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.
Advisories
Source ID Title
Github GHSA Github GHSA GHSA-ch7q-53v8-73pc authentik's invitation expiry is delayed by at least 5 minutes
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

Thu, 20 Nov 2025 19:00:00 +0000

Type Values Removed Values Added
First Time appeared Goauthentik
Goauthentik authentik
CPEs cpe:2.3:a:goauthentik:authentik:*:*:*:*:*:*:*:*
Vendors & Products Goauthentik
Goauthentik authentik

Thu, 20 Nov 2025 16:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 19 Nov 2025 21:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 19 Nov 2025 17:15:00 +0000

Type Values Removed Values Added
Description 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.
Title authentik invitation expiry is delayed by at least 5 minutes
Weaknesses CWE-613
References
Metrics cvssV3_1

{'score': 5.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2025-11-20T15:48:29.627Z

Reserved: 2025-11-10T14:07:42.921Z

Link: CVE-2025-64708

cve-icon Vulnrichment

Updated: 2025-11-19T21:10:45.925Z

cve-icon NVD

Status : Analyzed

Published: 2025-11-19T17:15:52.220

Modified: 2025-11-20T18:56:40.587

Link: CVE-2025-64708

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.