⚠ Withdrawn by GitHub Security Advisories

Withdrawn: July 31, 2026

GHSA-vmf9-6pcv-xr87MediumCVSS 5.3

Withdrawn Advisory: Username enumeration attack in goauthentik

Published
August 29, 2023
Last Modified
July 31, 2026

🔗 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:

🎯 Affected products2

  • npm/@goauthentik/api:>= 2023.6.0, < 2023.6.2
  • npm/@goauthentik/api:< 2023.5.6

🔗 References (5)