CVE-2025-53942: authentik has an insufficient check for account active status during OAuth/SAML authentication
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.57% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: goauthentik.io (Go) 0.0.0-20250722122105-7a4c6b9b50f8; govulncheck-vulndb (openSUSE:Leap 15.6) 0.0.20250814T182633-150000.1.98.1; govulncheck-vulndb (openSUSE:Tumbleweed) 0.0.20250811T192933-1.1.
Low priority for now. Upgrade to goauthentik.io (Go) 0.0.0-20250722122105-7a4c6b9b50f8; govulncheck-vulndb (openSUSE:Leap 15.6) 0.0.20250814T182633-150000.1.98.1; govulncheck-vulndb (openSUSE:Tumbleweed) 0.0.20250811T192933-1.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
authentik is an open-source Identity Provider that emphasizes flexibility and versatility, with support for a wide set of protocols. In versions 2025.4.4 and earlier, as well as versions 2025.6.0-rc1 through 2025.6.3, deactivated users who registered through OAuth/SAML or linked their accounts to OAuth/SAML providers can still retain partial access to the system despite their accounts being deactivated. They end up in a half-authenticated state where they cannot access the API but crucially they can authorize applications if they know the URL of the application. To workaround this issue, developers can add an expression policy to the user login stage on the respective authentication flow with the expression of return request.context["pending_user"].is_active. This modification ensures that the return statement only activates the user login stage when the user is active. This issue is fixed in versions authentik 2025.4.4 and 2025.6.4.
- Published
- Jul 23, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 48th percentile
- CWE
- CWE-269
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 7.1
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| goauthentik | authentik | cpe:2.3:a:goauthentik:authentik |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
goauthentik authentik
- <= 2025.4.3, < 2025.4.4, >= 2025.6.0-rc1, < 2025.6.4affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- goauthentik authentikbefore 2025.4.4
- goauthentik authentik2025.6.0 and later · before 2025.6.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | goauthentik.io | from 0 | — |
| Go | goauthentik.io | before 0.0.0-20250722122105-7a4c6b9b50f8 | 0.0.0-20250722122105-7a4c6b9b50f8 |
| openSUSE:Leap 15.6 | govulncheck-vulndb | before 0.0.20250814T182633-150000.1.98.1 | 0.0.20250814T182633-150000.1.98.1 |
| openSUSE:Tumbleweed | govulncheck-vulndb | before 0.0.20250811T192933-1.1 | 0.0.20250811T192933-1.1 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP6 | govulncheck-vulndb | before 0.0.20250814T182633-150000.1.98.1 | 0.0.20250814T182633-150000.1.98.1 |
Same product
goauthentik: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-49448authentik: SourceStage bypass via empty POST39Monitor
- CVE-2024-38371Insufficient access control for OAuth2 Device Code flow in authentik39Monitor
- CVE-2023-48228OAuth2: PKCE can be fully circumvented39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-29928Mar 28, 2025 · authentik's deletion of sessions did not revoke sessions when using database session storage32Monitor
- ← EarlierCVE-2025-52553Jun 27, 2025 · authentik has Insufficient Session verification for Remote Access Control endpoint access22Monitor
- Later →CVE-2025-64521Nov 19, 2025 · authentik deactivated service accounts can authenticate to OAuth19Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:goauthentik.io | 0.0.0-20250722122105-7a4c6b9b50f8 | Package registry (OSV) |
| opensuse:govulncheck-vulndb | 0.0.20250814T182633-150000.1.98.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:govulncheck-vulndb | 0.0.20250814T182633-150000.1.98.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-94609428 days apartauthentik: Privilege Escalation to Superuser via Group Hierarchy35Monitor
- CVE-2026-40172303 days apartauthentik: Privilege Escalation via User PATCH: Superuser Group Assignment Bypasses enable_group_superuser32Monitor
Not on record for this CVE: EPSS history · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-269 · Improper Privilege ManagementCVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Root cause
To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.
The bug in code
The whole CWE-269 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
kind: ClusterRole
rules:
- apiGroups: ["*"]
resources: ["*"]
verbs: ["*"]Fixed
kind: Role
metadata:
namespace: lodos-system
rules:
- apiGroups: ["apps"]
resources: ["deployments"]
verbs: ["get", "list", "update"]Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.