Servers and applications
CVE-2026-54730
Google Chrome device trust stages can be bypassed
- Severity
- High 8.6
- Published
- 15 Jul 2026
- Last changed
- 15 Jul 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 2026.2.6, 2026.5.5
- Exploit chance
- 0.7% in the next 30 daysHigher than 53% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Read data · Change data
- CVSS vector
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- Also known as
- GHSA-3v9h-3hrm-29cx
- Sources
- Project advisories (GitHub)
Description
The enterprise Google Chrome device-trust stages advance the flow without confirming that the out-of-band device attestation actually ran. An attacker who can reach such a stage can skip the verification iframe and pass the device-trust gate, completing authentication from a device that was never verified.
Affected: enterprise deployments that place a Google Chrome device-trust stage in a flow: either an Endpoint stage backed by a Google Chrome connector set to mode = REQUIRED (present in 2026.5 only), or the deprecated Google Chrome Device Trust Connector (GDTC) stage (present in all supported versions). Not affected: deployments that use neither stage, and Endpoint stages left at the default mode = OPTIONAL, which is not intended to block the flow.
The device attestation happens out-of-band, in a verification iframe that calls Google's Verified Access API and records the verified device on success.
Workarounds
None. We recommend not relying on the Google Chrome Endpoint stage or the GDTC stage as a security control until you upgrade.
Affected software
| Software | Affected versions |
|---|---|
authentikServers and applications · github:goauthentik/authentik |
|
About authentik
The authentication glue you need.
- Total installations
- 1 millionauthentik
- GitHub stars
- 26,351GitHub, 15 Nov 2026
- Forks
- 2,134GitHub, 15 Nov 2026
- Latest release
- version/2026.8.5GitHub, 15 Nov 2026
- Released
- 21 Oct 2026GitHub
- First published on GitHub
- 30 Dec 2019GitHub
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 2026.8 | 2026.8.5 | Yes |
| 2026.5 | 2026.5.8 | Yes |
| 2026.2 | 2026.2.7 | Ended 18 Aug 2026 |
| 2025.12 | 2025.12.6 | Ended 22 May 2026 |
| 2025.10 | 2025.10.4 | Ended 24 Feb 2026 |
| 2025.8 | 2025.8.6 | Ended 13 Jan 2026 |
From endoflife.date.
Vulnerabilities in authentik
- In our list
- 48
- Published in the last 12 months
- 24
- Critical, last 12 months
- 3
- High, last 12 months
- 17
- Known exploited
- 0
- CVE-2026-94613Denial of Service via Malformed SAML MessagesHigh 7.5 9 Sept 2026
- CVE-2026-94611Certain stored credentials readable with view permission aloneHigh 8.1 9 Sept 2026
- CVE-2026-94612Authentication bypass in SAML Sources via assertion confusion and replayHigh 7.4 9 Sept 2026
- CVE-2026-94609Privilege escalation via delegated group and user managementHigh 8.8 9 Sept 2026
- CVE-2026-94606MFA bypass via recipient override in the email authenticatorHigh 8.9 9 Sept 2026
- GHSA-hmrg-vpp4-gj88Broken access control in Shared Signals Framework stream managementMedium 5.4 15 Jul 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-54730
- GitHub Advisory Database https://github.com/advisories/GHSA-3v9h-3hrm-29cx
- github.com https://github.com/goauthentik/authentik/security/advisories/GHSA-3v9h-3hrm-29cx