CVE-2026-100606

HIGHPre-NVD 7.77.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-87701 (ENISA EUVD) · GHSA-mgrx-3hqw-485h (GitHub Security Advisories)Source: ENISA EUVD

7.7EG
EchelonGraph verdictPlan mitigationNo fix is confirmed yet: check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.7Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (VulnCheck) lists FlowiseAI Flowise versions up to and including 3.1.4 as affected. No release containing a fix is confirmed on record.

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.7HIGHmedium confidence
EG Risk
51
EG Risk 51/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity77% × 45%
Impact severity (EG Severity): CVSS 7.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.7): severity, escalated by confirmed exploitation. This CVE's 7.7 is its impact severity (EG Severity), not escalated.

EG Severity
7.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-16). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 26, 2026

Last Modified

September 28, 2026

Advisory Details (2)

Auto-updated Sep 26, 2026
No fix on record yet. Sources: github.
Web page

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 advisoryMentions a patch (unverified)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 120 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 20 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-21 16:37 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-11-19 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  4. 2026-11-19 01:26 UTCOSV refresh
  5. 2026-11-18 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-11-17 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-11-17 10:53 UTCEchelonGraph re-scored
  8. 2026-11-16 16:47 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  9. 2026-11-15 16:53 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-11-14 16:38 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  12. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  13. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  14. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  15. 2026-11-09 19:41 UTCEchelonGraph re-scored
  16. 2026-11-09 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-11-08 16:37 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  18. 2026-11-07 16:37 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  19. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  21. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  22. 2026-11-03 16:45 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-11-02 17:37 UTCEchelonGraph re-scored
  24. 2026-11-02 17:37 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7
  25. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.5% · 40th percentile
Show 75 more
  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  2. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  3. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  4. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  6. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  7. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  8. 2026-10-26 15:32 UTCEchelonGraph re-scored
  9. 2026-10-26 15:32 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7
  10. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-10-25 15:58 UTCEchelonGraph re-scored
  12. 2026-10-24 22:17 UTCEchelonGraph re-scored
  13. 2026-10-24 22:17 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7
  14. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  16. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  21. 2026-10-18 05:11 UTCEchelonGraph re-scored
  22. 2026-10-17 20:14 UTCEchelonGraph re-scored
  23. 2026-10-17 20:14 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7
  24. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  25. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  26. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  27. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  28. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  29. 2026-10-12 16:41 UTCEchelonGraph re-scored
  30. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  31. 2026-10-11 22:12 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7
  32. 2026-10-11 20:16 UTCEchelonGraph re-scored
  33. 2026-10-11 18:29 UTCEchelonGraph re-scored
  34. 2026-10-11 15:02 UTCEchelonGraph re-scored
  35. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  36. 2026-10-11 09:20 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7
  37. 2026-10-10 20:27 UTCEchelonGraph re-scored
  38. 2026-10-10 20:27 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7
  39. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  40. 2026-10-10 07:35 UTCEchelonGraph re-scored
  41. 2026-10-10 07:35 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7
  42. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  43. 2026-10-09 18:38 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7
  44. 2026-10-09 05:47 UTCEchelonGraph re-scored
  45. 2026-10-09 05:47 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7
  46. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  47. 2026-10-08 16:55 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7
  48. 2026-10-08 01:05 UTCEchelonGraph re-scored
  49. 2026-10-08 01:05 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7
  50. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  51. 2026-10-07 12:12 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7
  52. 2026-10-06 23:20 UTCEchelonGraph re-scored
  53. 2026-10-06 23:20 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7
  54. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  55. 2026-10-06 10:29 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7
  56. 2026-10-05 21:37 UTCEchelonGraph re-scored
  57. 2026-10-05 21:37 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7
  58. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  59. 2026-10-05 08:29 UTCEchelonGraph re-scored
  60. 2026-10-05 08:29 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7
  61. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  62. 2026-10-04 19:38 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7
  63. 2026-10-04 06:46 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7
  64. 2026-10-03 17:55 UTCEchelonGraph re-scored
  65. 2026-10-03 17:54 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7
  66. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  67. 2026-10-03 05:01 UTCEchelonGraph re-scored
  68. 2026-10-03 05:01 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7
  69. 2026-10-02 16:09 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7
  70. 2026-10-02 03:18 UTCEchelonGraph re-scored
  71. 2026-10-02 03:18 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7
  72. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  73. 2026-10-01 14:24 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7
  74. 2026-10-01 01:33 UTCEchelonGraph re-scored
  75. 2026-10-01 01:33 UTCGHSA enrichmentGHSA-mgrx-3hqw-485h · GitHub severity CRITICAL · GitHub CVSS 7.7

Frequently asked(5)

What is CVE-2026-100606?
CVE-2026-100606 is a high-severity vulnerability; its CVE record was 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 made public?
CVE-2026-100606 was made public on September 10, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on September 26, 2026. EchelonGraph's copy of the record carries a last-modified date of September 28, 2026; the record at its source may have been updated since.
Is CVE-2026-100606 actively exploited?
CVE-2026-100606 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st 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?
No fix for CVE-2026-100606 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix. The CVE record's CNA (VulnCheck) lists FlowiseAI Flowise versions up to and including 3.1.4 as affected. No release containing a fix is confirmed on record.

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.