CVE-2026-91937

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

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

Flowise before 3.1.4 fails to sanitize the overrideConfig.sessionId parameter before using it in MongoDB queries within the MongoDBMemory node. Unauthenticated attackers can submit MongoDB operator objects through the prediction API to read chat history records belonging to other users from the shared collection.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/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 computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 15, 2026

Advisory Details (2)

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

Flowise before 3.1.4 NoSQL Injection via sessionId | Advisories | VulnCheck

https://www.vulncheck.com/advisories/flowise-before-3.1.4-nosql-injection-via-sessionid
github Patch Available🟡 PoC Available

Cross-Session Data Leakage via NoSQL Injection in MongoDBMemory Node · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-wpvf-4vfx-rgxm

Vendor Advisories for CVE-2026-91937(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 18× in last 7d / 18× 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-09-19 01:50 UTCEG score recompute
  2. 2026-09-19 01:50 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 12:50 UTCGHSA enrichment
  5. 2026-09-17 23:49 UTCEG score recompute
  6. 2026-09-17 23:49 UTCGHSA enrichment
  7. 2026-09-17 19:32 UTCEPSS rescore
  8. 2026-09-17 10:12 UTCGHSA enrichment
  9. 2026-09-16 21:12 UTCEG score recompute
  10. 2026-09-16 21:12 UTCGHSA enrichment
  11. 2026-09-16 14:09 UTCEPSS rescore
  12. 2026-09-16 07:35 UTCGHSA enrichment
  13. 2026-09-15 18:33 UTCEG score recompute
  14. 2026-09-15 18:33 UTCGHSA enrichment
  15. 2026-09-15 17:23 UTCEG score recompute
  16. 2026-09-15 16:33 UTCEG score recompute
  17. 2026-09-15 15:24 UTCEG score recompute
  18. 2026-09-15 15:22 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-91937?
CVE-2026-91937 is a high vulnerability published on September 15, 2026. Flowise before 3.1.4 fails to sanitize the overrideConfig.sessionId parameter before using it in MongoDB queries within the MongoDBMemory node. Unauthenticated attackers can submit MongoDB operator objects through the prediction API to read chat history records belonging to other users from the…
When was CVE-2026-91937 disclosed?
CVE-2026-91937 was first published in the National Vulnerability Database on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-91937 actively exploited?
CVE-2026-91937 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.6% of all scored CVEs.
What is the CVSS score of CVE-2026-91937?
CVE-2026-91937 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-91937?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-91937, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-91937?

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

Start Free Scan →Browse All CVEs