How severe is CVE-2023-39522?

CVE-2023-39522 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.

Is CVE-2023-39522 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (40th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2023-39522?

CVE-2023-39522 affects Goauthentik Authentik. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2023-39522?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2023-39522 published?

CVE-2023-39522 was published on 2023-08-29 and last updated on 2026-06-17.

CVE-2023-39522

CVE-2023-39522 is a medium-severity vulnerability in Goauthentik Authentik with a CVSS 3.x base score of 5.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-203.

Key facts

Severity: Medium (CVSS 3.x base score 5.3)
EPSS exploit prediction: 1% (40th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-203
Affected product: Goauthentik Authentik
Published: 2023-08-29
Last modified: 2026-06-17

Description

goauthentik is an open-source Identity Provider. In affected versions using a recovery flow with an identification stage an attacker is able to determine if a username exists. 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. 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. This issue has been addressed in versions 2023.5.6 and 2023.6.2. Users are advised to upgrade. There are no known workarounds for this issue.

Frequently asked questions

What is CVE-2023-39522?: goauthentik is an open-source Identity Provider. In affected versions using a recovery flow with an identification stage an attacker is able to determine if a username exists. 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. 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. This issue has been addressed in versions 2023.5.6 and 2023.6.2. Users are advised to upgrade. There are no known workarounds for this issue.
How severe is CVE-2023-39522?: CVE-2023-39522 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2023-39522 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (40th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2023-39522?: CVE-2023-39522 affects Goauthentik Authentik. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2023-39522?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2023-39522 published?: CVE-2023-39522 was published on 2023-08-29 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:goauthentik:authentik:*:*:*:*:*:*:*:*

More vulnerabilities in Goauthentik Authentik

CVE-2026-49448 — Critical (CVSS 9.8): authentik is an open-source identity provider. Prior to versions 2025.12.6, 2026.2.4, and 2026.5.1, the Source stage…
CVE-2024-52289 — Critical (CVSS 9.8): authentik is an open-source identity provider. Redirect URIs in the OAuth2 provider in authentik are checked by RegEx…
CVE-2025-52553 — Critical (CVSS 9.6): authentik is an open-source identity provider. After authorizing access to a RAC endpoint, authentik creates a token…
CVE-2023-46249 — Critical (CVSS 9.6): authentik is an open-source Identity Provider. Prior to versions 2023.8.4 and 2023.10.2, when the default admin user…
CVE-2022-23555 — Critical (CVSS 9.4): authentik is an open-source Identity Provider focused on flexibility and versatility. Versions prior to 2022.11.4 and…
CVE-2026-42849 — Critical (CVSS 9.3): authentik is an open-source identity provider. Prior to versions 2025.12.5 and 2026.2.3, due to the implementation of…

All CVEs affecting Goauthentik Authentik →

Other CWE-203 (Observable Discrepancy) vulnerabilities

CVE-2019-25337 — Critical (CVSS 9.8): OwnCloud 8.1.8 contains a username enumeration vulnerability that allows remote attackers to discover user accounts by…
CVE-2026-23519 — Critical (CVSS 9.8): RustCrypto CMOV provides conditional move CPU intrinsics which are guaranteed on major platforms to execute in…
CVE-2025-27667 — Critical (CVSS 9.8): Vasion Print (formerly PrinterLogic) before Virtual Appliance Host 22.0.843 Application 20.0.1923 allows Administrative…
CVE-2024-25714 — Critical (CVSS 9.8): In Rhonabwy through 1.1.13, HMAC signature verification uses a strcmp function that is vulnerable to side-channel…
CVE-2024-25191 — Critical (CVSS 9.8): php-jwt 1.0.0 uses strcmp (which is not constant time) to verify authentication, which makes it easier to bypass…
CVE-2024-25190 — Critical (CVSS 9.8): l8w8jwt 2.2.1 uses memcmp (which is not constant time) to verify authentication, which makes it easier to bypass…

Browse all CWE-203 (Observable Discrepancy) vulnerabilities →