CVE-2026-54730
authentik Chrome device-trust can be bypassed to authenticate unverified devices
Is CVE-2026-54730 being exploited?
Not confirmed. CVE-2026-54730 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.37% probability of exploitation in the next 30 days.
How severe is CVE-2026-54730?
CVE-2026-54730 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-54730?
Yes. A fix has been recorded for CVE-2026-54730. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-54730 affect?
CVE-2026-54730 affects authentik versions prior to 2026.2.6 and 2026.5.5, Google Chrome Endpoint stage (mode=REQUIRED), Google Chrome Device Trust Connector stage. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-54730?
Upgrade to 2026.2.6 or 2026.5.5; review auth flows; block unverified devices
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authentication bypass: attacker can skip Google Chrome device attestation stage and log in from an unverified device after primary credential use.
Immediate action required
- affected< 2026.2.6
- affected>= 2026.5.0 and < 2026.5.5
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.