CVE-2026-100606

HIGHPre-NVD 7.77.7—
EchelonGraph scoreHIGH confidence

Score 7.7 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-26. A secondary CVSS source baseline 7.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
7.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.7Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.7
EG Score
7.7HIGHhigh confidence
EG Risk
51
EG Risk 51/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
Severity77% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
29th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (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

September 26, 2026

Last Modified

September 28, 2026

Advisory Details (2)

Auto-updated Sep 26, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Flowise through 3.1.4 Authentication Bypass via SSO Email Match | Advisories | VulnCheck

https://www.vulncheck.com/advisories/flowise-through-3.1.4-authentication-bypass-via-sso-email-match
github Patch Available🟡 PoC Available

INVITED users auto-promoted via SSO email match (invite-token bypass) · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-vf3j-89vf-r697

Vendor Advisories for CVE-2026-100606(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 28× in last 7d / 33× 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-04 06:46 UTCGHSA enrichment
  2. 2026-10-03 17:55 UTCEG score recompute
  3. 2026-10-03 17:54 UTCGHSA enrichment
  4. 2026-10-03 14:25 UTCEPSS rescore
  5. 2026-10-03 05:01 UTCEG score recompute
  6. 2026-10-03 05:01 UTCGHSA enrichment
  7. 2026-10-02 16:09 UTCGHSA enrichment
  8. 2026-10-02 03:18 UTCEG score recompute
  9. 2026-10-02 03:18 UTCGHSA enrichment
  10. 2026-10-01 19:49 UTCEPSS rescore
  11. 2026-10-01 14:24 UTCGHSA enrichment
  12. 2026-10-01 01:33 UTCEG score recompute
  13. 2026-10-01 01:33 UTCGHSA enrichment
  14. 2026-09-30 15:02 UTCEPSS rescore
  15. 2026-09-30 12:42 UTCGHSA enrichment
  16. 2026-09-29 23:48 UTCEG score recompute
  17. 2026-09-29 23:48 UTCGHSA enrichment
  18. 2026-09-29 15:20 UTCEPSS rescore
  19. 2026-09-29 08:11 UTCEG score recompute
  20. 2026-09-29 08:11 UTCGHSA enrichment
  21. 2026-09-28 19:20 UTCEG score recompute
  22. 2026-09-28 19:20 UTCGHSA enrichment
  23. 2026-09-28 18:09 UTCEG score recompute
  24. 2026-09-28 18:09 UTCGHSA enrichment
  25. 2026-09-28 13:50 UTCEPSS rescore
Show 8 more
  1. 2026-09-28 05:12 UTCGHSA enrichment
  2. 2026-09-27 16:20 UTCEG score recompute
  3. 2026-09-27 16:20 UTCGHSA enrichment
  4. 2026-09-27 03:29 UTCEG score recompute
  5. 2026-09-27 03:29 UTCGHSA enrichment
  6. 2026-09-26 14:35 UTCEG score recompute
  7. 2026-09-26 13:40 UTCEG score recompute
  8. 2026-09-26 13:30 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-100606?
CVE-2026-100606 is a high vulnerability published on September 26, 2026. 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…
When was CVE-2026-100606 disclosed?
CVE-2026-100606 was first published on September 26, 2026, with the most recent update on September 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-100606 actively exploited?
CVE-2026-100606 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100606?
CVE-2026-100606 has a CVSS base score of 7.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100606?
A fix for CVE-2026-100606 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100606 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-100606?

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

Book a Demo →Browse All CVEs