CVE-2026-94611

HIGHPre-NVD 8.18.1
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: secondary
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 8.1Exploit: 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.7, 2026.5.7, and 2026.8.2, authentik API serializers return stored credentials when an account has view permission on an affected configuration, even when that account is not authorized to change the configuration or read its secrets. Affected configurations include one-time code delivery by mail or SMS, outbound provisioning targets, device trust integrations, identity sources, the Kubernetes outpost integration, applications using a client or shared secret, and applications using a proxy provider. Deployments are affected when view permission is granted to accounts that are not intended to read these credentials; deployments where every viewer is permitted to read them are not affected. This issue is fixed in versions 2026.2.7, 2026.5.7, and 2026.8.2.

CVSS v3
8.1
EG Score
8.1(low)
EG Risk
36(Track)
EG Risk 36/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
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

Published

September 24, 2026

Last Modified

September 24, 2026

Advisory Details (10)

Auto-updated Sep 24, 2026
Patch available. Sources: github, github_pr, github_commit.
generic

Release 2026.2 | authentik

https://docs.goauthentik.io/releases/2026.2#fixed-in-202627
github_commit

commit 77d2e24442c3 (goauthentik/authentik)

Fix landed in goauthentik/authentik commit 77d2e24442c3 — awaiting tagged release

https://github.com/goauthentik/authentik/commit/77d2e24442c3eb6e88010f40aa569a8bfb584f99
github_commit

commit 6bed64ef80a4 (goauthentik/authentik)

Fix landed in goauthentik/authentik commit 6bed64ef80a4 — awaiting tagged release

https://github.com/goauthentik/authentik/commit/6bed64ef80a4dd21011cce64c41b1e7c5640ecb3
github_commit

commit 5109a4d4998d (goauthentik/authentik)

Fix landed in goauthentik/authentik commit 5109a4d4998d — awaiting tagged release

https://github.com/goauthentik/authentik/commit/5109a4d4998d6a5ee399ca3e22ba546231c140c7
github_commit

commit 4b3fad38be44 (goauthentik/authentik)

Fix landed in goauthentik/authentik commit 4b3fad38be44 — awaiting tagged release

https://github.com/goauthentik/authentik/commit/4b3fad38be44ef3eef1f0baf83e7b3061229eb99
github_pr

security: automated internal backport of patch 1751-secrets-read-permission.sec.patch to authentik-main

Fix merged in goauthentik/authentik PR #25970 on 2026-09-09 — awaiting tagged release

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

security: automated internal backport of patch 1751-secrets-read-permission.sec.patch to authentik-2026.8

Fix merged in goauthentik/authentik PR #25965 on 2026-09-09 — awaiting tagged release

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

security: automated internal backport of patch 1751-secrets-read-permission.sec.patch to authentik-2026.5

Fix merged in goauthentik/authentik PR #25960 on 2026-09-09 — awaiting tagged release

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

security: automated internal backport of patch 1751-secrets-read-permission.sec.patch to authentik-2026.2

Fix merged in goauthentik/authentik PR #25955 on 2026-09-09 — awaiting tagged release

https://github.com/goauthentik/authentik/pull/25955
github Patch Available

Certain stored credentials readable with view permission alone · Advisory · goauthentik/authentik · GitHub

https://github.com/goauthentik/authentik/security/advisories/GHSA-m9h4-7j9c-55x9

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 4× 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-09-24 18:36 UTCEG score recompute
  2. 2026-09-24 17:18 UTCEG score recompute
  3. 2026-09-24 16:27 UTCEG score recompute
  4. 2026-09-24 16:26 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2026-94611?
CVE-2026-94611 is a high vulnerability published on September 24, 2026. authentik is an open-source identity provider. Prior to 2026.2.7, 2026.5.7, and 2026.8.2, authentik API serializers return stored credentials when an account has view permission on an affected configuration, even when that account is not authorized to change the configuration or read its secrets.…
When was CVE-2026-94611 disclosed?
CVE-2026-94611 was first published in the National Vulnerability Database on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-94611?
CVE-2026-94611 has a CVSS v3 base score of 8.1 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-94611?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-94611, 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-94611

Explore →

Is Your Infrastructure Affected by CVE-2026-94611?

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

Book a Demo →Browse All CVEs