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.7% (50th percentile of EPSS-scored CVEs). 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.7%CVSS: 8.6Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

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.6HIGHmedium confidence
EG Risk
39
EG Risk 39/100CISA SSVC

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%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
50th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 18, 2026

Last Modified

September 8, 2026

Advisory Details (5)

Auto-updated Aug 18, 2026
Fix named in the CVE record. Sources: github_commit, github_pr, github.
githubMentions a patch (unverified)

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 11× in last 7d / 52× 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-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 21:39 UTCEG score recompute
  5. 2026-10-06 15:18 UTCEPSS rescore
  6. 2026-10-06 08:22 UTCEG score recompute
  7. 2026-10-05 17:43 UTCEPSS rescore
  8. 2026-10-05 09:37 UTCEG score recompute
  9. 2026-10-04 23:22 UTCEPSS rescore
  10. 2026-10-03 17:38 UTCEG score recompute
  11. 2026-10-03 14:26 UTCEPSS rescore
  12. 2026-10-03 02:37 UTCEG score recompute
  13. 2026-10-02 17:56 UTCEPSS rescore
  14. 2026-10-02 01:28 UTCEG score recompute
  15. 2026-10-01 19:50 UTCEPSS rescore
  16. 2026-09-30 21:19 UTCEG score recompute
  17. 2026-09-30 15:03 UTCEPSS rescore
  18. 2026-09-30 09:48 UTCEG score recompute
  19. 2026-09-29 15:22 UTCEPSS rescore
  20. 2026-09-28 21:56 UTCEG score recompute
  21. 2026-09-28 13:51 UTCEPSS rescore
  22. 2026-09-27 19:31 UTCEG score recompute
  23. 2026-09-27 13:48 UTCEPSS rescore
  24. 2026-09-27 07:55 UTCEG score recompute
  25. 2026-09-26 15:59 UTCEPSS rescore
Show 69 more
  1. 2026-09-25 01:27 UTCEG score recompute
  2. 2026-09-24 14:04 UTCEPSS rescore
  3. 2026-09-23 20:19 UTCEG score recompute
  4. 2026-09-23 17:54 UTCEPSS rescore
  5. 2026-09-22 20:25 UTCEG score recompute
  6. 2026-09-22 08:19 UTCEG score recompute
  7. 2026-09-20 21:50 UTCEG score recompute
  8. 2026-09-20 20:16 UTCEPSS rescore
  9. 2026-09-19 22:51 UTCEG score recompute
  10. 2026-09-18 21:51 UTCEG score recompute
  11. 2026-09-18 19:28 UTCEPSS rescore
  12. 2026-09-17 21:49 UTCEG score recompute
  13. 2026-09-17 19:31 UTCEPSS rescore
  14. 2026-09-16 21:56 UTCEG score recompute
  15. 2026-09-16 14:08 UTCEPSS rescore
  16. 2026-09-16 10:08 UTCEG score recompute
  17. 2026-09-16 05:15 UTCEPSS rescore
  18. 2026-09-15 09:09 UTCEG score recompute
  19. 2026-09-15 03:11 UTCEPSS rescore
  20. 2026-09-13 22:41 UTCEG score recompute
  21. 2026-09-13 16:47 UTCEPSS rescore
  22. 2026-09-12 23:43 UTCEG score recompute
  23. 2026-09-12 00:43 UTCEG score recompute
  24. 2026-09-11 14:53 UTCEPSS rescore
  25. 2026-09-11 13:14 UTCEG score recompute
  26. 2026-09-10 12:36 UTCEG score recompute
  27. 2026-09-10 09:35 UTCEPSS rescore
  28. 2026-09-09 08:46 UTCEG score recompute
  29. 2026-09-08 22:01 UTCEPSS rescore
  30. 2026-09-07 21:54 UTCEG score recompute
  31. 2026-09-07 16:01 UTCEPSS rescore
  32. 2026-09-06 22:11 UTCEG score recompute
  33. 2026-09-06 13:47 UTCEPSS rescore
  34. 2026-09-05 23:08 UTCEG score recompute
  35. 2026-09-05 00:07 UTCEG score recompute
  36. 2026-09-04 12:03 UTCEG score recompute
  37. 2026-09-04 05:06 UTCEPSS rescore
  38. 2026-09-02 23:55 UTCEG score recompute
  39. 2026-09-02 14:12 UTCEPSS rescore
  40. 2026-09-02 00:50 UTCEG score recompute
  41. 2026-09-01 13:54 UTCEPSS rescore
  42. 2026-09-01 13:22 UTCEG score recompute
  43. 2026-09-01 04:40 UTCEPSS rescore
  44. 2026-08-31 01:49 UTCEG score recompute
  45. 2026-08-30 19:17 UTCEPSS rescore
  46. 2026-08-30 02:48 UTCEG score recompute
  47. 2026-08-30 01:22 UTCEPSS rescore
  48. 2026-08-29 03:49 UTCEG score recompute
  49. 2026-08-28 21:41 UTCEPSS rescore
  50. 2026-08-27 21:40 UTCEG score recompute
  51. 2026-08-27 14:25 UTCEPSS rescore
  52. 2026-08-26 22:41 UTCEG score recompute
  53. 2026-08-26 14:46 UTCEPSS rescore
  54. 2026-08-25 23:38 UTCEG score recompute
  55. 2026-08-25 13:49 UTCEPSS rescore
  56. 2026-08-25 00:39 UTCEG score recompute
  57. 2026-08-24 13:07 UTCEG score recompute
  58. 2026-08-23 02:39 UTCEG score recompute
  59. 2026-08-23 00:19 UTCEPSS rescore
  60. 2026-08-22 03:41 UTCEG score recompute
  61. 2026-08-21 23:49 UTCEPSS rescore
  62. 2026-08-21 04:43 UTCEG score recompute
  63. 2026-08-20 22:55 UTCEPSS rescore
  64. 2026-08-19 18:15 UTCEG score recompute
  65. 2026-08-19 17:04 UTCEPSS rescore
  66. 2026-08-18 18:23 UTCEG score recompute
  67. 2026-08-18 17:21 UTCEG score recompute
  68. 2026-08-18 17:07 UTCEG score recompute
  69. 2026-08-18 17:04 UTCMITRE cvelistV5first tracked

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 on August 18, 2026, with the most recent update on September 8, 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.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54730?
CVE-2026-54730 has a CVSS base score of 8.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54730?
The CVE record for CVE-2026-54730 names the fix: "This issue is fixed in versions 2026.2.6 and 2026.5.5."

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.