BIT-authentik-2023-26481

See a problem?
Import Source
https://github.com/bitnami/vulndb/tree/main/data/authentik/BIT-authentik-2023-26481.json
JSON Data
https://api.osv.dev/v1/vulns/BIT-authentik-2023-26481
Aliases
Published
2026-04-16T23:36:01.864Z
Modified
2026-04-17T04:57:16.877765591Z
Summary
Insufficient user check in FlowTokens by Email stage
Details

authentik is an open-source Identity Provider. Due to an insufficient access check, a recovery flow link that is created by an admin (or sent via email by an admin) can be used to set the password for any arbitrary user. This attack is only possible if a recovery flow exists, which has both an Identification and an Email stage bound to it. If the flow has policies on the identification stage to skip it when the flow is restored (by checking request.context['is_restored']), the flow is not affected by this. With this flow in place, an administrator must create a recovery Link or send a recovery URL to the attacker, who can, due to the improper validation of the token create, set the password for any account. Regardless, for custom recovery flows it is recommended to add a policy that checks if the flow is restored, and skips the identification stage. This issue has been fixed in versions 2023.2.3, 2023.1.3 and 2022.12.2.

Database specific
{
    "cpes": [
        "cpe:2.3:a:goauthentik:authentik:*:*:*:*:*:*:*:*"
    ],
    "severity": "Medium"
}
References

Affected packages

Bitnami / authentik

Package

Name
authentik
Purl
pkg:bitnami/authentik

Severity

  • 6.5 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N CVSS Calculator

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
2022.12.3
Type
SEMVER
Events
Introduced
2023.1.0
Last affected
2023.1.3
Introduced
2023.2.0
Last affected
2023.2.3

Database specific

source
"https://github.com/bitnami/vulndb/tree/main/data/authentik/BIT-authentik-2023-26481.json"