CVE-2026-54730: goauthentik authentik · Improper Access Control
Affects goauthentik authentikSource CVE Database V5
Not known to be exploited · CVSS 8.6 High : upgrade to 2026.5.5 or 2026.2.6 soon.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.5.5, 2026.2.6
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Aug 2026
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 15 Nov 2026.
What to do
Upgrade authentik and goauthentik/authentik to 2026.5.5 or 2026.2.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| goauthentikauthentik | Affected
| Fixed in
|
| goauthentikauthentik | Affected
| Fixed in
|
GitHubgoauthentik/authentikpkg:github/goauthentik/authentikOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade affected authentik deployments to version 2026.2.6 or 2026.5.5 or later, where this issue is fixed. No other mitigation is indicated by the vendor advisory. Patch status is confirmed by the version information in the description.
Description
authentik is an open-source identity provider. Prior to 2026.2.6 and 2026.5.5, the enterprise Google Chrome device-trust stages advance the flow without confirming that the out-of-band device attestation actually ran. Affected enterprise deployments place either a Google Chrome Endpoint stage with mode set to REQUIRED or the deprecated Google Chrome Device Trust Connector stage in an authentication flow. The device attestation occurs in a verification iframe that calls the Google Verified Access API and records the verified device on success, but the vulnerable stages treat the flow as passed as soon as the stage is submitted. An attacker who can reach such a stage, including after primary username and password authentication, can skip the verification iframe and authenticate from a device that was never verified. Where device trust is the only additional factor, that protection is fully bypassed, while other configured factors remain in force. This issue is fixed in versions 2026.2.6 and 2026.5.5.
References
- github.com/goauthentik/authentik/security/advisories/GHSA-3v9h-3hrm-29cx (opens in a new tab)
- github.com/goauthentik/authentik/pull/24053 (opens in a new tab)
- github.com/goauthentik/authentik/pull/24058 (opens in a new tab)
- github.com/goauthentik/authentik/commit/27866a94f29d0d7f784b3c462a697a968d3f6b9c (opens in a new tab)
- github.com/goauthentik/authentik/commit/85adb0bbbd7ad4f2807ec21cf25bb42aee81afbc (opens in a new tab)
- github.com/goauthentik/authentik/releases/tag/version/2026.2.6 (opens in a new tab)
- github.com/goauthentik/authentik/releases/tag/version/2026.5.5 (opens in a new tab)