HighCVE-2026-94611

    authentik: Stored credentials are readable with view permission alone (CVE-2026-94611)

    Published Last modified Sources: CVE.org, OSV

    Share

    What is affected, what to do

    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.

    Update Goauthentik Authentik to version 2026.2.7.

    Affected
    • Goauthentik Authentik gte 2026.5.0, < 2026.5.7..*
    • Goauthentik Authentik lt *..2026.2.7
    Fixed in
    • Goauthentik Authentik 2026.2.7

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    8.1

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    8.1

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: CVE.org, OSV

    0.3 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 26.8

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    73.49 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    8.1 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    8.1
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.3 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    26.8
    Elevated — this CVE ranks above at least 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 24 September 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-200, CWE-522

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    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.

    Source: NVD (NIST), OSV (Open Source Vulnerabilities), cvelistv5

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    goauthentikauthentik
    • < 2026.2.7
    • ≥ 2026.5.0, < 2026.5.7
    • 2026.2.7
    • —
    Distribution and container packages (2)

    Downstream packages (e.g. Bitnami, Debian, Ubuntu, Red Hat). Versions refer to the distribution, not the vendor.

    Distribution and container packages
    Affected versionsFixed in
    bitnamiauthentik
    • 2026.5.0
    • 2026.8.0
    • —
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-200Exposure of Sensitive Information to an Unauthorized Actor

      Class

      The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

      Entry at MITRE CWE-200

    • CWE-522Insufficiently Protected Credentials

      Class

      The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.

      Entry at MITRE CWE-522

    References & sources

    • github.comgoauthentik/authentik/security/advisories/GHSA-m9h4-7j9c-55x9x_refsource_CONFIRM
    • github.comgoauthentik/authentik/pull/25955x_refsource_MISC
    • github.comgoauthentik/authentik/pull/25960x_refsource_MISC
    • github.comgoauthentik/authentik/pull/25965x_refsource_MISC
    • github.comgoauthentik/authentik/pull/25970x_refsource_MISC
    • github.comgoauthentik/authentik/commit/4b3fad38be44ef3eef1f0baf83e7b30612…x_refsource_MISC
    • github.comgoauthentik/authentik/commit/5109a4d4998d6a5ee399ca3e22ba546231…x_refsource_MISC
    • github.comgoauthentik/authentik/commit/6bed64ef80a4dd21011cce64c41b1e7c56…x_refsource_MISC
    • github.comgoauthentik/authentik/commit/77d2e24442c3eb6e88010f40aa569a8bfb…x_refsource_MISC
    • docs.goauthentik.ioreleases/2026.2x_refsource_MISC
    • docs.goauthentik.ioreleases/2026.5x_refsource_MISC
    • docs.goauthentik.ioreleases/2026.8x_refsource_MISC
    • github.comgoauthentik/authentik/releases/tag/version/2026.2.7x_refsource_MISC
    • github.comgoauthentik/authentik/releases/tag/version/2026.5.7x_refsource_MISC
    • github.comgoauthentik/authentik/releases/tag/version/2026.8.2x_refsource_MISC
    • NVD (NIST)vuln/detail/CVE-2026-94611web

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: none known, automatable: no

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentadded
      —
      {"id":"CVE-2026-94611","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-09-24T17:07:45.172270Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. ReceivedGitHub

      CVSS V3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

      Weakness type: CWE-200, CWE-522

      Description added or changed

      Show 20 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      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.
      CVSSadded
      —
      AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
      Weakness type (CWE)added
      —
      CWE-200
      Weakness type (CWE)added
      —
      CWE-522
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/94xxx/CVE-2026-94611.json">CVE-2026-94611</a>
      Referenceadded
      —
      https://docs.goauthentik.io/releases/2026.2#fixed-in-202627
      Referenceadded
      —
      https://docs.goauthentik.io/releases/2026.5#fixed-in-202657
      Referenceadded
      —
      https://docs.goauthentik.io/releases/2026.8#fixed-in-202682
      Referenceadded
      —
      https://github.com/goauthentik/authentik/commit/4b3fad38be44ef3eef1f0baf83e7b3061229eb99
      Referenceadded
      —
      https://github.com/goauthentik/authentik/commit/5109a4d4998d6a5ee399ca3e22ba546231c140c7
      Referenceadded
      —
      https://github.com/goauthentik/authentik/commit/6bed64ef80a4dd21011cce64c41b1e7c5640ecb3
      Referenceadded
      —
      https://github.com/goauthentik/authentik/commit/77d2e24442c3eb6e88010f40aa569a8bfb584f99
      Referenceadded
      —
      https://github.com/goauthentik/authentik/pull/25955
      Referenceadded
      —
      https://github.com/goauthentik/authentik/pull/25960
      Referenceadded
      —
      https://github.com/goauthentik/authentik/pull/25965
      Referenceadded
      —
      https://github.com/goauthentik/authentik/pull/25970
      Referenceadded
      —
      https://github.com/goauthentik/authentik/releases/tag/version/2026.2.7
      Referenceadded
      —
      https://github.com/goauthentik/authentik/releases/tag/version/2026.5.7
      Referenceadded
      —
      https://github.com/goauthentik/authentik/releases/tag/version/2026.8.2
      Referenceadded
      —
      https://github.com/goauthentik/authentik/security/advisories/GHSA-m9h4-7j9c-55x9

      Source identifier: security-advisories@github.com

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-94611
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-94611"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-94611.svg?lang=en" alt="CVE-2026-94611 – NEOSEC Intel" height="20"></a>