CVE-2026-54730

HIGHPre-NVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 70% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.6Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.6
EG Score
8.6(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity86% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

August 18, 2026

Last Modified

August 18, 2026

Advisory Details (5)

Auto-updated Aug 18, 2026
Patch available. Sources: github_commit, github_pr, github.
github Patch Available

Google Chrome device trust stages can be bypassed · Advisory · goauthentik/authentik · GitHub

https://github.com/goauthentik/authentik/security/advisories/GHSA-3v9h-3hrm-29cx
github_pr

security: automated internal backport of patch 1817.sec.patch to authentik-2026.5

Fix merged in goauthentik/authentik PR #24058 on 2026-07-15 — awaiting tagged release

https://github.com/goauthentik/authentik/pull/24058
github_pr

security: automated internal backport of patch 1817.sec.patch to authentik-2026.2

Fix merged in goauthentik/authentik PR #24053 on 2026-07-15 — awaiting tagged release

https://github.com/goauthentik/authentik/pull/24053
github_commit

commit 85adb0bbbd7a (goauthentik/authentik)

Fix landed in goauthentik/authentik commit 85adb0bbbd7a — awaiting tagged release

https://github.com/goauthentik/authentik/commit/85adb0bbbd7ad4f2807ec21cf25bb42aee81afbc
github_commit

commit 27866a94f29d (goauthentik/authentik)

Fix landed in goauthentik/authentik commit 27866a94f29d — awaiting tagged release

https://github.com/goauthentik/authentik/commit/27866a94f29d0d7f784b3c462a697a968d3f6b9c

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 16× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 23:38 UTCEG score recompute
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-25 00:39 UTCEG score recompute
  4. 2026-08-24 13:07 UTCEG score recompute
  5. 2026-08-23 02:39 UTCEG score recompute
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-22 03:41 UTCEG score recompute
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-21 04:43 UTCEG score recompute
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-19 18:15 UTCEG score recompute
  12. 2026-08-19 17:04 UTCEPSS rescore
  13. 2026-08-18 18:23 UTCEG score recompute
  14. 2026-08-18 17:21 UTCEG score recompute
  15. 2026-08-18 17:07 UTCEG score recompute
  16. 2026-08-18 17:04 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54730?
CVE-2026-54730 is a high vulnerability published on August 18, 2026. 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…
When was CVE-2026-54730 disclosed?
CVE-2026-54730 was first published in the National Vulnerability Database on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54730 actively exploited?
CVE-2026-54730 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 69.8% of all scored CVEs.
What is the CVSS score of CVE-2026-54730?
CVE-2026-54730 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-54730?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54730, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-54730

Explore →

Is Your Infrastructure Affected by CVE-2026-54730?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs