CVE-2026-100609

MEDIUMPre-NVD 6.86.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Flowise (npm packages flowise and flowise-components) through 3.1.4 looks up credentials by ID without filtering on the requesting user's workspace (findOneBy({ id: credentialId }) with no workspaceId condition) in several code paths: getAllOpenaiAssistants/getSingleOpenaiAssistant (GET /api/v1/openai-assistants and /api/v1/openai-assistants/:id), uploadFilesToAssistant (POST /api/v1/openai-assistants-file/upload/), deleteAssistant (DELETE /api/v1/assistants/:id, reachable by first importing a poisoned assistant row via POST /api/v1/export-import/import), and the shared helper used by getVoices (GET /api/v1/text-to-speech/voices). An authenticated user of one workspace can supply a credential UUID belonging to another workspace, causing the server to decrypt and use that workspace's OpenAI or ElevenLabs API key on the attacker's behalf. No patched version was available at the time of publication.

CVSS v3
6.8
EG Score
6.8MEDIUMhigh confidence
EG Risk
47
EG Risk 47/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
Severity68% × 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.2%
EPSS %ILE
12th
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 30, 2026

Advisory Details (2)

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

Flowise through 3.1.4 Insecure Direct Object Reference via Credential | Advisories | VulnCheck

https://www.vulncheck.com/advisories/flowise-through-3.1.4-insecure-direct-object-reference-via-credential
github Patch Available🟡 PoC Available

Cross-Workspace Credential IDOR · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-27w2-26m5-x82c

Vendor Advisories for CVE-2026-100609(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 21× in last 7d / 24× 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-03 15:20 UTCEG score recompute
  2. 2026-10-03 15:20 UTCGHSA enrichment
  3. 2026-10-03 14:25 UTCEPSS rescore
  4. 2026-10-02 14:39 UTCEG score recompute
  5. 2026-10-02 14:39 UTCGHSA enrichment
  6. 2026-10-01 19:49 UTCEPSS rescore
  7. 2026-10-01 14:01 UTCEG score recompute
  8. 2026-10-01 14:01 UTCGHSA enrichment
  9. 2026-09-30 15:02 UTCEPSS rescore
  10. 2026-09-30 13:24 UTCEG score recompute
  11. 2026-09-30 13:24 UTCGHSA enrichment
  12. 2026-09-30 13:00 UTCEG score recompute
  13. 2026-09-30 12:59 UTCGHSA enrichment
  14. 2026-09-29 16:46 UTCEG score recompute
  15. 2026-09-29 16:46 UTCGHSA enrichment
  16. 2026-09-29 15:20 UTCEPSS rescore
  17. 2026-09-28 15:52 UTCEG score recompute
  18. 2026-09-28 15:52 UTCGHSA enrichment
  19. 2026-09-28 13:50 UTCEPSS rescore
  20. 2026-09-27 15:14 UTCEG score recompute
  21. 2026-09-27 15:14 UTCGHSA enrichment
  22. 2026-09-26 14:35 UTCEG score recompute
  23. 2026-09-26 13:40 UTCEG score recompute
  24. 2026-09-26 13:30 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-100609?
CVE-2026-100609 is a medium vulnerability published on September 26, 2026. Flowise (npm packages flowise and flowise-components) through 3.1.4 looks up credentials by ID without filtering on the requesting user's workspace (findOneBy({ id: credentialId }) with no workspaceId condition) in several code paths: getAllOpenaiAssistants/getSingleOpenaiAssistant (GET…
When was CVE-2026-100609 disclosed?
CVE-2026-100609 was first published on September 26, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-100609 actively exploited?
CVE-2026-100609 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100609?
CVE-2026-100609 has a CVSS base score of 6.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100609?
A fix for CVE-2026-100609 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100609 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-100609?

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

Book a Demo →Browse All CVEs