CriticalCVE-2026-100606

    Flowise: Improper Authentication (CVE-2026-100606)

    Published Last modified Sources: BSI

    Share

    What is affected, what to do

    Flowise through 3.1.4 (Enterprise/platform mode with SSO enabled) contains an authentication bypass in the SSO login path. When an SSO callback arrives with an email matching a user whose status is INVITED, verifyAndLogin (SSOBase.ts:80-94) copies the user record from the database — including the server-stored single-use invitation tempToken — into the data passed to AccountService.register().

    The available sources name no fixed version. Check the vendor guidance in the references below.

    Affected
    • Flowise lte *..3.1.4

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

    Metrics

    9.2

    Priority

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

    Source: Vendor (CNA), CVSS v4

    7.7

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: BSI

    0.5 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 40.9

    Show all metrics
    Severity
    Critical
    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
    75.50 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
    9.2 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
    7.7
    CVSS v4

    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
    9.2
    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.5 %
    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
    40.9
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    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: proof of concept · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 28 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-287

    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

    Flowise through 3.1.4 (Enterprise/platform mode with SSO enabled) contains an authentication bypass in the SSO login path. When an SSO callback arrives with an email matching a user whose status is INVITED, verifyAndLogin (SSOBase.ts:80-94) copies the user record from the database — including the server-stored single-use invitation tempToken — into the data passed to AccountService.register(). The register handler's token lookup, email match, and expiry checks therefore pass trivially against the server's own token instead of a caller-supplied one, and the account and its organization membership are flipped to ACTIVE. As a result, anyone able to authenticate at any configured SSO provider using a pending invitee's email address as the email claim can take over that invitation and obtain the invited user's access to the organization without ever possessing the emailed invitation token, for as long as the invitation is valid (24 hours by default). At the time of the advisory no patched version was available.

    Source: BSI WID Portal

    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
    FlowiseAIFlowise
    • ≤ 3.1.4
    • —
    Open SourceFlowise
    • ≤ 3.1.4
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-287Improper Authentication

      Class

      When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

      Entry at MITRE CWE-287

    References & sources

    • github.comGitHub Security Advisory (GHSA-jvx3-mjpw-r4gh)Vendor advisory
    • vulncheck.comVulnCheck Advisory: Flowise through 3.1.4 Missing Authorization via upsert-historyThird-party advisory
    • github.comGitHub Security Advisory (GHSA-vf3j-89vf-r697)Vendor advisory
    • vulncheck.comVulnCheck Advisory: Flowise through 3.1.4 Authentication Bypass via SSO Email MatchThird-party advisory
    • github.comGitHub Security Advisory (GHSA-rpcc-gw54-mfgx)Vendor advisory
    • vulncheck.comVulnCheck Advisory: Flowise through 3.1.4 Authorization Bypass via BullMQ DashboardThird-party advisory
    • github.comGitHub Security Advisory (GHSA-ppmg-4cx6-95hh)Vendor advisory
    • vulncheck.comVulnCheck Advisory: Flowise through 3.1.4 Missing Authorization via Chat Message RoutesThird-party advisory
    • github.comGitHub Security Advisory (GHSA-cffm-583c-vffr)Vendor advisory
    • vulncheck.comVulnCheck Advisory: Flowise through 3.1.4 Authentication Bypass via Email-Only SSOThird-party advisory
    • github.comGitHub Security Advisory (GHSA-27w2-26m5-x82c)Vendor advisory
    • vulncheck.comVulnCheck Advisory: Flowise through 3.1.4 Insecure Direct Object Reference via CredentialThird-party advisory

    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: proof of concept, automatable: no

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-vf3j-89vf-r697
      SSVC assessmentadded
      —
      {"id":"CVE-2026-100606","role":"CISA Coordinator","options":[{"exploitation":"poc"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-09-28T19:08:17.212056Z"}

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

    2. ReceivedVulnCheck

      CVSS V4.0: AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

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

      Weakness type: CWE-287

      Description added or changed

      Show 7 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      Flowise through 3.1.4 (Enterprise/platform mode with SSO enabled) contains an authentication bypass in the SSO login path. When an SSO callback arrives with an email matching a user whose status is INVITED, verifyAndLogin (SSOBase.ts:80-94) copies the user record from the database — including the server-stored single-use invitation tempToken — into the data passed to AccountService.register(). The register handler's token lookup, email match, and expiry checks therefore pass trivially against the server's own token instead of a caller-supplied one, and the account and its organization membership are flipped to ACTIVE. As a result, anyone able to authenticate at any configured SSO provider using a pending invitee's email address as the email claim can take over that invitation and obtain the invited user's access to the organization without ever possessing the emailed invitation token, for as long as the invitation is valid (24 hours by default). At the time of the advisory no patched version was available.
      CVSSadded
      —
      AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
      CVSSadded
      —
      AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L
      Weakness type (CWE)added
      —
      CWE-287
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/100xxx/CVE-2026-100606.json">CVE-2026-100606</a>
      Referenceadded
      —
      https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-vf3j-89vf-r697
      Referenceadded
      —
      https://www.vulncheck.com/advisories/flowise-through-3.1.4-authentication-bypass-via-sso-email-match

      Source identifier: disclosure@vulncheck.com

    Linked CVEs

    Linked CVEs
    HighCVE-2026-100610Flowise through 3.1.4 Missing Authorization via upsert-history7.5—
    HighCVE-2026-100609Flowise through 3.1.4 Insecure Direct Object Reference via Credential6.8—
    HighCVE-2026-100608Flowise through 3.1.4 Authorization Bypass via BullMQ Dashboard8.3—
    CriticalCVE-2026-100607Flowise through 3.1.4 Authentication Bypass via Email-Only SSO7.7—
    CriticalCVE-2026-100606Flowise through 3.1.4 Authentication Bypass via SSO Email Match7.7—
    HighCVE-2026-100605Flowise through 3.1.4 Missing Authorization via Chat Message Routes7.1—
    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-100606
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-100606"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-100606.svg?lang=en" alt="CVE-2026-100606 – NEOSEC Intel" height="20"></a>