{"items":[{"id":"NVI-00015041","kind":"vulnerability","title":"Withdrawn Advisory: Username enumeration attack in goauthentik","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"disputed","identifiers":["GHSA-vmf9-6pcv-xr87","CVE-2023-39522"],"plain_summary":"GitHub lists this reviewed advisory for @goauthentik/api, @goauthentik/api. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-0ebe4ea8c42dbb01af95d8a1d20fbb00"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-31T22:37:04.000Z","value":"5.3 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-0f338dba2c9459a41d79b4e0a97a289a"},{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"0.620%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.4975. Missing scores are unknown.","source_id":"sr-0ebe4ea8c42dbb01af95d8a1d20fbb00"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-0f338dba2c9459a41d79b4e0a97a289a","url":"https://github.com/advisories/GHSA-vmf9-6pcv-xr87","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-vmf9-6pcv-xr87","publisher":"GitHub Advisory Database","observed_at":"2026-11-03T09:58:33.950Z"},{"id":"sr-0ebe4ea8c42dbb01af95d8a1d20fbb00","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2023-39522","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:42:56.080Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0f338dba2c9459a41d79b4e0a97a289a"],"technology":"@goauthentik/api","known_exclusions":[],"conditions_summary":"### Withdrawn Advisory\nThis advisory has been withdrawn due to an incorrect package mapping error. This link is maintained to preserve external references.\n\n### Original Description\n## Summary\nUsing a recovery flow with an identification stage an attacker is able to determine if a username exists.\n\n## Impact\nOnly 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.\n\n## Details\n\nAn 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.\n\nThe 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\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n-   Email us at security@goauthentik.io","public_affected_ranges":[">= 2023.6.0, < 2023.6.2"]},{"certainty":"source_listed","source_ids":["sr-0f338dba2c9459a41d79b4e0a97a289a"],"technology":"@goauthentik/api","known_exclusions":[],"conditions_summary":"### Withdrawn Advisory\nThis advisory has been withdrawn due to an incorrect package mapping error. This link is maintained to preserve external references.\n\n### Original Description\n## Summary\nUsing a recovery flow with an identification stage an attacker is able to determine if a username exists.\n\n## Impact\nOnly 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.\n\n## Details\n\nAn 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.\n\nThe 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\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n-   Email us at security@goauthentik.io","public_affected_ranges":["< 2023.5.6"]}],"null_published_at":"2026-11-06T00:29:57.259Z","source_updated_at":"2026-07-31T22:37:04.000Z","source_disclosed_at":"2023-08-29T23:34:51.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-11-03T09:58:33.950Z"},{"id":"NVI-00015041","kind":"vulnerability","title":"Withdrawn Advisory: Username enumeration attack in goauthentik","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"withdrawn","identifiers":["GHSA-vmf9-6pcv-xr87","CVE-2023-39522"],"plain_summary":"GitHub lists this reviewed advisory for @goauthentik/api, @goauthentik/api. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-0f338dba2c9459a41d79b4e0a97a289a"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-31T22:37:04.000Z","value":"5.3 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-0f338dba2c9459a41d79b4e0a97a289a"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-0f338dba2c9459a41d79b4e0a97a289a","url":"https://github.com/advisories/GHSA-vmf9-6pcv-xr87","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-vmf9-6pcv-xr87","publisher":"GitHub Advisory Database","observed_at":"2026-11-03T09:58:33.950Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0f338dba2c9459a41d79b4e0a97a289a"],"technology":"@goauthentik/api","known_exclusions":[],"conditions_summary":"### Withdrawn Advisory\nThis advisory has been withdrawn due to an incorrect package mapping error. This link is maintained to preserve external references.\n\n### Original Description\n## Summary\nUsing a recovery flow with an identification stage an attacker is able to determine if a username exists.\n\n## Impact\nOnly 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.\n\n## Details\n\nAn 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.\n\nThe 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\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n-   Email us at security@goauthentik.io","public_affected_ranges":[">= 2023.6.0, < 2023.6.2"]},{"certainty":"source_listed","source_ids":["sr-0f338dba2c9459a41d79b4e0a97a289a"],"technology":"@goauthentik/api","known_exclusions":[],"conditions_summary":"### Withdrawn Advisory\nThis advisory has been withdrawn due to an incorrect package mapping error. This link is maintained to preserve external references.\n\n### Original Description\n## Summary\nUsing a recovery flow with an identification stage an attacker is able to determine if a username exists.\n\n## Impact\nOnly 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.\n\n## Details\n\nAn 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.\n\nThe 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\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n-   Email us at security@goauthentik.io","public_affected_ranges":["< 2023.5.6"]}],"null_published_at":"2026-11-03T10:03:26.539Z","source_updated_at":"2026-07-31T22:37:04.000Z","source_disclosed_at":"2023-08-29T23:34:51.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-03T09:58:33.950Z"}],"next_cursor":null,"snapshot_revision":"42594"}