Vulnerabilities in pkg:npm/@goauthentik/api
PACKAGECVE-2023-39522 is a MODERATE (CVSS 5.3) username enumeration attack vulnerability (CWE-203: Observable Discrepancy) affecting Withdrawn Advisory libraries in the npm ecosystem. The issue involves username enumeration attack in goauthentik. Remediation is available by upgrading affected packages to version 2023.6.2, 2023.5.6.
pkg:npm/@goauthentik/api
Vulnerability advisories affecting package pkg:npm/@goauthentik/api. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-vmf9-6pcv-xr87 | CVE-2023-39522 | MODERATE | Withdrawn Advisory: Username enumeration attack in goauthentik |
CVE-2023-39522 at a Glance
Security Impact
CVSS: 5.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N).
How to Fix CVE-2023-39522
To remediate this vulnerability, upgrade all affected Withdrawn Advisory dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install @goauthentik/api@2023.6.2
npm install @goauthentik/api@2023.5.6
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls @goauthentik/api
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2023-39522, inspect your project dependencies using npm:
npm ls @goauthentik/api
Analyze the terminal output to locate any version of Withdrawn Advisory in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2023.6.2), your application is affected.
Note: The npm ls @goauthentik/api command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-203: Observable Discrepancy, where the product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor. In Withdrawn Advisory, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2023-39522 Affected Withdrawn Advisory Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@goauthentik/api
|
npm |
≥ 2023.6.0
< 2023.6.2
|
2023.6.2
|
|
@goauthentik/api
|
npm |
< 2023.5.6
|
2023.5.6
|
References
Frequently Asked Questions
What is CVE-2023-39522?
Which Withdrawn Advisory versions are affected?
What version fixes CVE-2023-39522?
Is @goauthentik/api affected?
What is the CVSS score of CVE-2023-39522?
What CWE is associated with CVE-2023-39522?
How can I check npm dependencies for CVE-2023-39522?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-vmf9-6pcv-xr87",
"modified" : "2026-07-31T22:35:59Z",
"published" : "2023-08-29T23:34:51Z",
"withdrawn" : "2026-07-31T22:35:59Z",
"aliases" : [ "CVE-2023-39522" ],
"summary" : "Withdrawn Advisory: Username enumeration attack in goauthentik",
"details" : "### 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](mailto:security@goauthentik.io)",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "@goauthentik/api"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2023.6.0"
}, {
"fixed" : "2023.6.2"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "@goauthentik/api"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2023.5.6"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/goauthentik/authentik/security/advisories/GHSA-vmf9-6pcv-xr87"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-39522"
}, {
"type" : "WEB",
"url" : "https://github.com/github/advisory-database/pull/8720#pullrequestreview-4726968365"
}, {
"type" : "WEB",
"url" : "https://github.com/goauthentik/authentik/commit/aa874dd92a770d5f8cd8f265b7cdd31cd73a4599"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/goauthentik/authentik"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-203" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2023-08-29T23:34:51Z",
"nvd_published_at" : "2023-08-29T18:15:08Z"
}
}