Skip to main content

Security Policy

authentik takes security very seriously. We follow the rules of responsible disclosure, and we urge our community to do so as well, instead of reporting vulnerabilities publicly. This allows us to patch the issue quickly, announce it's existence and release the fixed version.

Independent audits and pentests

In May/June of 2023 Cure53 conducted an audit and pentest. The results are published on the Cure53 website. For more details about authentik's response to the findings of the audit refer to 2023-06 Cure53 Code audit.

What authentik classifies as a CVE

CVE (Common Vulnerability and Exposure) is a system designed to aggregate all vulnerabilities. As such, a CVE will be issued when there is a either vulnerability or exposure. Per NIST, A vulnerability is:

“Weakness in an information system, system security procedures, internal controls, or implementation that could be exploited or triggered by a threat source.”

If it is determined that the issue does qualify as a CVE, a CVE number will be issued to the reporter from GitHub.

Even if the issue is not a CVE, we still greatly appreciate your help in hardening authentik.

Supported Versions

(.x being the latest patch release for each version)


Reporting a Vulnerability

To report a vulnerability, send an email to Be sure to include relevant information like which version you've found the issue in, instructions on how to reproduce the issue, and anything else that might make it easier for us to find the issue.

Severity levels

authentik reserves the right to reclassify CVSS as necessary. To determine severity, we will use the CVSS calculator from NVD ( The calculated CVSS score will then be translated into one of the following categories:

0.1 – 3.9Low
4.0 – 6.9Medium
7.0 – 8.9High
9.0 – 10.0Critical

Disclosure process

  1. Report from Github or Issue is reported via Email as listed above.
  2. The authentik Security team will try to reproduce the issue and ask for more information if required.
  3. A severity level is assigned.
  4. A fix is created, and if possible tested by the issue reporter.
  5. The fix is backported to other supported versions, and if possible a workaround for other versions is created.
  6. An announcement is sent out with a fixed release date and severity level of the issue. The announcement will be sent at least 24 hours before the release of the security fix.
  7. The fixed version is released for the supported versions.

Getting security notifications

To get security notifications, subscribe to the mailing list here or join the discord server.