EOL.Wiki EOL.Wiki
← ← Back to all products

Authentik

Active
Security & Networking Latest Version: 2025.12.4 Latest Release: Feb 12, 2026

authentik is an open-source identity provider for authentication, authorization, and user management.

Versions

9

Latest Version

2025.12.4

Active Support

2

EOL

7

Lifecycle Timeline

Today
2025.12
2025.12
2025.10
2025.10
2025.8
2025.8
2025.6
2025.6
2025.4
2025.4
2024.12
2024.12
2023.10
2023.10
2022.12
2022.12
2021.12
2021.12
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
2025.12Jan 13, 2026-No2025.12.4No
Active
2025.10Oct 27, 2025-No2025.10.4No
Active
2025.8Aug 20, 2025-Jan 13, 20262025.8.6No
EOL
2025.6Jun 3, 2025-Oct 27, 20252025.6.4No
EOL
2025.4Apr 29, 2025-Aug 20, 20252025.4.4No
EOL
2024.12Dec 19, 2024-Apr 30, 20252024.12.5No
EOL
2023.10Oct 26, 2023-Apr 24, 20242023.10.7No
EOL
2022.12Dec 28, 2022-Feb 14, 20232022.12.3No
EOL
2021.12Dec 16, 2021-Feb 16, 20222021.12.5No
EOL

Frequently Asked Questions

Which versions of Authentik have reached end of life?
The following Authentik versions have reached end of life and no longer receive security updates: 2025.8, 2025.6, 2025.4, 2024.12, 2023.10, 2022.12, 2021.12. It is recommended to upgrade to a supported version.
Is it safe to continue using Authentik 2025.8?
Authentik 2025.8 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Authentik?
The latest version of Authentik is 2025.12.4, released in the 2025.12 release cycle.
How many versions of Authentik are currently supported?
Authentik currently has 2 actively supported version(s): 2025.12, 2025.10.
When does Authentik 2025.12 reach end of life?
Authentik 2025.12 does not have a specific end-of-life date announced yet.
What should I do when Authentik reaches end of life?
When a Authentik version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.