---
id: CVE-2026-54730
title: authentik is an open-source identity provider
summary: >-
  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…
severity: none
cwe:
  - CWE-284
  - CWE-807
published: '2026-08-18'
updated: '2026-09-08'
sourceUpdated: '2026-09-08T21:02:26.047'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-54730'
references:
  - url: >-
      https://github.com/goauthentik/authentik/commit/27866a94f29d0d7f784b3c462a697a968d3f6b9c
    label: security-advisories@github.com
  - url: >-
      https://github.com/goauthentik/authentik/commit/85adb0bbbd7ad4f2807ec21cf25bb42aee81afbc
    label: security-advisories@github.com
  - url: 'https://github.com/goauthentik/authentik/pull/24053'
    label: security-advisories@github.com
  - url: 'https://github.com/goauthentik/authentik/pull/24058'
    label: security-advisories@github.com
  - url: 'https://github.com/goauthentik/authentik/releases/tag/version/2026.2.6'
    label: security-advisories@github.com
  - url: 'https://github.com/goauthentik/authentik/releases/tag/version/2026.5.5'
    label: security-advisories@github.com
  - url: >-
      https://github.com/goauthentik/authentik/security/advisories/GHSA-3v9h-3hrm-29cx
    label: security-advisories@github.com
tags:
  - nvd
epss: 0.0068
epssPercentile: 0.50344
ingestedAt: '2026-09-08T21:11:12.282Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.