Authentik · Lifecycle Status

Authentik End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Authentik versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

Authentik 2025.12.4 is actively supported. No versions approaching EOL in the next 6 months.
Latest Active
2025.12.4
2025.12 series
Next EOL
None upcoming
Active Versions
2
of 10 total
EOL Versions
8
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 202220232024202520262021.122022.122023.102024.122025.42025.62025.82025.102025.122026.2TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
2021.12 2021.12.5 Dec 16, 2021 Feb 16, 2022 1543 days past EOL EOL
2022.12 2022.12.3 Dec 28, 2022 Feb 14, 2023 1180 days past EOL EOL
2023.10 2023.10.7 Oct 26, 2023 Apr 24, 2024 745 days past EOL EOL
2024.12 2024.12.5 Dec 19, 2024 Apr 30, 2025 374 days past EOL EOL
2025.4 2025.4.4 Apr 29, 2025 Aug 20, 2025 262 days past EOL EOL
2025.6 2025.6.4 Jun 3, 2025 Oct 27, 2025 194 days past EOL EOL
2025.8 2025.8.6 Aug 20, 2025 Jan 13, 2026 116 days past EOL EOL
2025.10 2025.10.4 Oct 27, 2025 Feb 24, 2026 74 days past EOL EOL
2025.12 2025.12.4 Jan 13, 2026 Already EOL Supported Active
2026.2 2026.2.2 Feb 24, 2026 Already EOL Supported Active

What does Authentik end of life mean for your organization?

When a Authentik version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.

Organizations running EOL Authentik should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Check your full stack for EOL risk

Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.

Open Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for Authentik?
See the full table above for all Authentik version EOL dates.
What is the latest supported version of Authentik?
The latest active version of Authentik is 2025.12.4. Always verify against the table above as support windows can change.
What happens when Authentik reaches end of life?
When Authentik reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Authentik?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Authentik versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →