Flowise before 3.1.4 fails to enforce workspace-level authorization checks in openai-realtime endpoints, allowing authenticated users to access tools from ChatFlows in other workspaces by supplying an unscoped chatflowid. Attackers can invoke GET and POST requests to retrieve tool definitions and execute tools from victim workspaces, triggering external side effects and accessing sensitive tool outputs.
CVE-2026-91933
Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-15. a secondary CVSS source baseline 7.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(high)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
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 computedSeverity71% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 26%
- KEV
- Not listed
Published
September 15, 2026
Last Modified
September 17, 2026
Advisory Details (2)
Auto-updated Sep 15, 2026Flowise before 3.1.4 Authorization Bypass via openai-realtime | Advisories | VulnCheck
https://www.vulncheck.com/advisories/flowise-before-3.1.4-authorization-bypass-via-openai-realtimeopenai-realtime endpoints allow cross-workspace tool disclosure and execution via unscoped chatflow ID · Advisory · FlowiseAI/Flowise · GitHub
https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-gggp-6qmf-xwwcVendor Advisories for CVE-2026-91933(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 26× in last 7d / 26× 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.
- 2026-09-21 00:28 UTCEG score recompute
- 2026-09-21 00:28 UTCGHSA enrichment
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-20 11:50 UTCGHSA enrichment
- 2026-09-19 23:02 UTCEG score recompute
- 2026-09-19 23:02 UTCGHSA enrichment
- 2026-09-19 10:24 UTCGHSA enrichment
- 2026-09-18 21:45 UTCEG score recompute
- 2026-09-18 21:45 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 09:07 UTCGHSA enrichment
- 2026-09-17 20:29 UTCEG score recompute
- 2026-09-17 20:29 UTCGHSA enrichment
- 2026-09-17 19:39 UTCEG score recompute
- 2026-09-17 19:39 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 09:45 UTCGHSA enrichment
- 2026-09-16 21:07 UTCGHSA enrichment
- 2026-09-16 17:55 UTCEG score recompute
- 2026-09-16 17:55 UTCGHSA enrichment
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 05:11 UTCEG score recompute
- 2026-09-16 05:11 UTCGHSA enrichment
- 2026-09-15 16:34 UTCEG score recompute
- 2026-09-15 15:24 UTCEG score recompute
Show 1 moreShow fewer
- 2026-09-15 15:22 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
Frequently asked(5)
What is CVE-2026-91933?
When was CVE-2026-91933 disclosed?
Is CVE-2026-91933 actively exploited?
What is the CVSS score of CVE-2026-91933?
How do I remediate CVE-2026-91933?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-91933
Is Your Infrastructure Affected by CVE-2026-91933?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.