⚠ Withdrawn by GitHub Security Advisories
Withdrawn: July 31, 2026
Withdrawn Advisory: Username enumeration attack in goauthentik
🔗 CVE IDs covered (1)
📋 Description
Withdrawn Advisory
This advisory has been withdrawn due to an incorrect package mapping error. This link is maintained to preserve external references.
Original Description
Summary
Using a recovery flow with an identification stage an attacker is able to determine if a username exists.
Impact
Only setups configured with a recovery flow are impacted by this. Anyone with a user account on a system with the recovery flow described above is susceptible to having their username/email revealed as existing.
Details
An attacker can easily enumerate and check users' existence using the recovery flow, as a clear message is shown when a user doesn't exist. Depending on configuration this can either be done by username, email, or both.
The invalid and valid usernames should both show the same message and always send an email. Article for reference here: https://postmarkapp.com/guides/password-reset-email-best-practices#how-to-make-sure-your-password-reset-emails-are-secure
For more information
If you have any questions or comments about this advisory:
- Email us at [email protected]
🎯 Affected products2
- npm/@goauthentik/api:>= 2023.6.0, < 2023.6.2
- npm/@goauthentik/api:< 2023.5.6
🔗 References (5)
- https://github.com/goauthentik/authentik/security/advisories/GHSA-vmf9-6pcv-xr87
- https://nvd.nist.gov/vuln/detail/CVE-2023-39522
- https://github.com/goauthentik/authentik/commit/aa874dd92a770d5f8cd8f265b7cdd31cd73a4599
- https://github.com/github/advisory-database/pull/8720#pullrequestreview-4726968365
- https://github.com/advisories/GHSA-vmf9-6pcv-xr87