CVE-2026-54730
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v4 Vector
Exploitability
Impact
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/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
Exploit Intelligence
Low risk: more likely to be exploited than 31% of all known CVEs.
References
Related Vulnerabilities
Other CWE-284 (Improper Access Control) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-27350 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2019-1653 | High | 7.5 | 100% | KEV | - |
| CVE-2023-23752 | Medium | 5.3 | 100% | KEV | Fix |
| CVE-2023-29298 | High | 7.5 | 100% | KEV | - |
| CVE-2023-38205 | High | 7.5 | 100% | KEV | - |
| CVE-2024-27348 | Critical | 9.8 | 99% | KEV | Fix |
Common questions
How do I fix CVE-2026-54730?
No published fix for CVE-2026-54730 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-54730 being actively exploited?
Not that we know of. CVE-2026-54730 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.37% is the estimated probability that it will be exploited in the next 30 days. That is higher than 31% of all scored CVEs.
How severe is CVE-2026-54730?
CVE-2026-54730 has a CVSS v4 base score of 8.6, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-54730
Markdown
[](https://tridentstack.com/cve/CVE-2026-54730)HTML
<a href="https://tridentstack.com/cve/CVE-2026-54730"><img src="https://tridentstack.com/cve/badge/CVE-2026-54730.svg" alt="CVE-2026-54730"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-18.