Advisory

GHSA-ch7q-53v8-73pc

Also known as: BIT-authentik-2025-64708, CVE-2025-64708, GO-2025-4136

Summary

authentik's invitation expiry is delayed by at least 5 minutes

Details

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:

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2025-11-19 18:47 UTC
Modified
2026-04-17 04:57 UTC

Affected packages and fixes

goauthentik.io

Go · All systems

Affected

  • introduced 0, fixed 0.0.0-20251119135424-6672e6aaa41e (semver)

Fixed versions

0.0.0-20251119135424-6672e6aaa41e

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences