# CVE-2026-54730: Auth bypass in authentik > Attackers can bypass Google Chrome device trust verification in authentik by skipping the attestation iframe, authenticating from unverified devices. - **Severity:** High 8.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:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 18 Aug 2026 - **Updated:** 18 Aug 2026 - **Also known as:** BIT-authentik-2026-54730, GHSA-3v9h-3hrm-29cx ## What is CVE-2026-54730? CVE-2026-54730 is a high-severity authentication bypass vulnerability in goauthentik authentik, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official 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. Weakness: CWE-807 (Reliance on Untrusted Inputs in a Security Decision), CWE-284 (Improper Access Control) ## Which versions are affected by CVE-2026-54730? 1 open source package ship an affected version, including authentik. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `authentik` | Bitnami | All versions | 2026.2.6, 2026.5.5 | ## How do I fix CVE-2026-54730? Upgrade authentik to a fixed version for your release line: 2026.2.6 or 2026.5.5. ## Is CVE-2026-54730 being exploited? There is no known exploitation of CVE-2026-54730 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-54730 and fix it if it is affected. What it is: CVE-2026-54730 is a high-severity authentication bypass vulnerability in goauthentik authentik, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-54730 in the wild and no public exploit code. Affected packages and fixed versions: - authentik (Bitnami): affected all versions; fixed in 2026.2.6, 2026.5.5 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-54730/ (Markdown: https://insights.sbomify.com/CVE-2026-54730/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54730 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54730 - OSV: https://osv.dev/vulnerability/CVE-2026-54730 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-54730/ Summaries are generated and may contain mistakes; the official description above is the record.