What is CVE-2023-39522?

CVE-2023-39522 is a medium-severity security vulnerability in @goauthentik/api (npm), affecting versions >= 2023.6.0, < 2023.6.2. It is fixed in 2023.6.2, 2023.5.6.

How severe is CVE-2023-39522?

CVE-2023-39522 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of @goauthentik/api are affected by CVE-2023-39522?

@goauthentik/api (npm) versions >= 2023.6.0, < 2023.6.2 is affected.

Is there a fix for CVE-2023-39522?

Yes. CVE-2023-39522 is fixed in 2023.6.2, 2023.5.6. Upgrade to this version or later.

Is CVE-2023-39522 exploitable, and should I be worried?

Whether CVE-2023-39522 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2023-39522 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2023-39522 in @goauthentik/api

Q: How severe is CVE-2023-39522?

CVE-2023-39522 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of @goauthentik/api are affected by CVE-2023-39522?

@goauthentik/api (npm) versions >= 2023.6.0, < 2023.6.2 is affected.

Q: Is there a fix for CVE-2023-39522?

Yes. CVE-2023-39522 is fixed in 2023.6.2, 2023.5.6. Upgrade to this version or later.

Q: Is CVE-2023-39522 exploitable, and should I be worried?

Whether CVE-2023-39522 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2023-39522 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2023-39522?

Upgrade: @goauthentik/api to 2023.6.2 or later, @goauthentik/api to 2023.5.6 or later.

Summary

Username enumeration attack in goauthentik

Using a recovery flow with an identification stage an attacker is able to determine if a username exists.

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]

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.

CVE-2023-39522 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2023.6.2, 2023.5.6); upgrading removes the vulnerable code path.

Affected versions

@goauthentik/api (>= 2023.6.0, < 2023.6.2) @goauthentik/api (< 2023.5.6)

Security releases

@goauthentik/api → 2023.6.2 (npm) @goauthentik/api → 2023.5.6 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

@goauthentik/api to 2023.6.2 or later; @goauthentik/api to 2023.5.6 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2023-39522? CVE-2023-39522 is a medium-severity security vulnerability in @goauthentik/api (npm), affecting versions >= 2023.6.0, < 2023.6.2. It is fixed in 2023.6.2, 2023.5.6.
How severe is CVE-2023-39522? CVE-2023-39522 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of @goauthentik/api are affected by CVE-2023-39522? @goauthentik/api (npm) versions >= 2023.6.0, < 2023.6.2 is affected.
Is there a fix for CVE-2023-39522? Yes. CVE-2023-39522 is fixed in 2023.6.2, 2023.5.6. Upgrade to this version or later.
Is CVE-2023-39522 exploitable, and should I be worried? Whether CVE-2023-39522 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2023-39522 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2023-39522?
- Upgrade @goauthentik/api to 2023.6.2 or later
- Upgrade @goauthentik/api to 2023.5.6 or later