VulnerabilityPublished 19 Nov 2025

CVE-2025-64521: Goauthentik.io · authentik allows a deactivated Service account to authenticate to OAuth

Affects goauthentik.ioSource GCVE Database

Compare

Authoritative record:CVE-2025-64521· Medium 4.8

Not known to be exploited · CVSS 4.8 Medium : upgrade to 0.0.0-20251119140106-9dbdfc3f1be0 when convenient.

Data as of 13 Nov 2026, 20:39 UTC

CVSS 3.1 base score

4.8Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	4.8

Patch: Available – fixed in 0.0.0-20251119140106-9dbdfc3f1be0

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade goauthentik.io to 0.0.0-20251119140106-9dbdfc3f1be0.

Affected software

Product	Affected	Fixed in
Gogoauthentik.io	Affected <0.0.0-20251119140106-9dbdfc3f1be0	Fixed in 0.0.0-20251119140106-9dbdfc3f1be0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in authentik version 0.0.0-20251119140106-9dbdfc3f1be0 and later (including 2025.8.5 and 2025.10.2). Users should upgrade to these fixed versions to resolve the issue. As a workaround, applications can implement a policy to explicitly check if the service account is active (e.g., by verifying request.user.is_active) and deny access if it is not. No other actions are required.

Description

A vulnerability in authentik's OAuth service account authentication allows deactivated service accounts to still authenticate using client credentials. This issue affects authentik versions prior to 0.0.0-20251119140106-9dbdfc3f1be0. The flaw does not affect other permissions or federation policies. Fixed versions are available, and a workaround involves adding a policy to explicitly check if the service account is active.

Impact

Deactivated service accounts could still authenticate to the OAuth provider, potentially allowing unauthorized access to resources or services that rely on this authentication. However, other permissions and federation policies are still enforced correctly, limiting the scope of impact. The CVSS score of 4.8 (medium severity) reflects limited confidentiality and integrity impact with no availability impact.

Summary

When authenticating with client_id and client_secret to an OAuth provider, authentik creates a service account for the provider. In versions before 0.0.0-20251119140106-9dbdfc3f1be0, authentication was possible even if the service account was deactivated, allowing potentially unauthorized access. Other permissions and federation policies remain correctly enforced. The issue is fixed in authentik versions 2025.8.5 and 2025.10.2 (represented by fixed version 0.0.0-20251119140106-9dbdfc3f1be0).

CWE-286Incorrect User Management (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product does not properly manage a user within its environment.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-289Authentication Bypass by Alternate Name (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product performs authentication based on the name of a resource being accessed, or the name of the actor performing the access, but it does not properly check all possible names for that resource or actor.
Architecture and Design · Input Validation
Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Nov 2026, 20:39 UTC

WeaknessesCWE-286, CWE-289

Technical details

References

Community reviews

Related threats