Stack Watch
Self-hosted update briefs — is it safe to update, or wait?
Disclaimer: Automated heuristics over public release notes and vulnerability databases (OSV / NVD). Can be wrong or incomplete. Always back up first and validate upgrades yourself. Stack Watch does not invent CVE IDs or issue counts. This is an MVP research project, not a live paid service.
Home / Authentik / version/2026.5.8

Authentik version/2026.5.8

SAFE

No breaking/security/wait signals detected in release notes heuristics.

Published: 2026-10-21T12:57:16Z · GitHub release

Summary of changes

See https://docs.goauthentik.io/docs/releases/2026.5#fixed-in-202658 ## What's Changed - ci: remove the Google Chrome apt source in setup (cherry-pick #25990 to version-2026.5) by @authentik-cherry-pick[bot] in #26011 - lib/expression: fix PickleError due to resolver match when using ak_call_policy (cherry-pick #25763 to version-2026.5) by @authentik-cherry-pick[bot] in #26071 - web/source/flows: fix flicker after webauthn (cherry-pick #25454 to version-2026.5) by @authentik-cherry-pick[bot] in #25835 - core: bump rustls (cherry-pick #26142 to version-2026.5) by @authentik-cherry-pick[bot] in #26144 - website: add umami (cherry-pick #26460 to version-2026.5) by @authentik-cherry-pick[bot] in #26462 - packages/django-channels-postgres: refresh pool credentials on connection attempts (cherry-pick #26505 to version-2026.5) by @authentik-cherry-pick[bot] in #26549 …

Breaking changes

None detected by heuristics.

CVEs linked to this release

None linked from release notes or OSV fixed-in match.

Linked issues / PRs mentioned

22

Back up first

Always back up first. Stack Watch briefs are automated heuristics over public release notes and vulnerability databases. They can be wrong or incomplete. You are responsible for validating upgrades in your own environment. We never invent CVE IDs or issue counts — if a number is missing, it was not found.