https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 21:34:25 +0000 https://cve.radiocsirt.org/vuln/bit-authentik-2025-64708 <p><strong>Affected:</strong> Bitnami: authentik</p> <p>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.</p> <p><strong>Affected:</strong> Bitnami: authentik</p> <p>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.</p> https://cve.radiocsirt.org/vuln/bit-authentik-2025-64708 https://cve.radiocsirt.org/vuln/euvd-2026-261460 EUVD-2026-261460 https://cve.radiocsirt.org/vuln/euvd-2026-261460 https://cve.radiocsirt.org/vuln/fkie_cve-2025-64708 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-64708 https://cve.radiocsirt.org/vuln/ghsa-ch7q-53v8-73pc <p><strong>Affected:</strong> Go: goauthentik.io</p> <p>### Summary</p> <p>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.</p> <p>### Patches</p> <p>authentik 2025.8.5 and 2025.10.2 fix this issue; for other versions the workaround below can be used.</p> <p>### Workarounds</p> <p>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.</p> <p>```python return not context[&#39;flow_plan&#39;].context[&#39;invitation&#39;].is_expired ```</p> <p>### For more information</p> <p>If users have any questions or comments about this advisory:</p> <p>- Email the authentik team at [security@goauthentik.io](mailto:security@goauthentik.io).</p> <p><strong>Affected:</strong> Go: goauthentik.io</p> <p>### Summary</p> <p>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.</p> <p>### Patches</p> <p>authentik 2025.8.5 and 2025.10.2 fix this issue; for other versions the workaround below can be used.</p> <p>### Workarounds</p> <p>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.</p> <p>```python return not context[&#39;flow_plan&#39;].context[&#39;invitation&#39;].is_expired ```</p> <p>### For more information</p> <p>If users have any questions or comments about this advisory:</p> <p>- Email the authentik team at [security@goauthentik.io](mailto:security@goauthentik.io).</p> https://cve.radiocsirt.org/vuln/ghsa-ch7q-53v8-73pc