CVE-2026-90534

MEDIUMNVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-09-12. NVD baseline CVSS 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

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

Flowise is a low-code platform for building LLM applications. In versions up to and including 3.1.3, the POST /api/v1/node-load-method/:name endpoint is mounted without any route-level permission check and invokes component loadMethods with an attacker-controlled nodeName, loadMethod, inputs, and credential value. The selected credential is resolved by raw Credential.id via getCredentialData() and decrypted without verifying Credential.workspaceId against the caller's active or shared workspace, unlike other credential read paths which are workspace-scoped. As a result, an authenticated low-privilege user (or workspace API key) in one workspace can supply a credential ID owned by another workspace and cause Flowise to act as a confused deputy, performing third-party provider calls with the victim workspace's credential and returning provider metadata to the attacker. Statically identified affected load methods include Google Drive listFiles, Google Sheets listSpreadsheets, and AWS DynamoDB KV Storage listTables. The raw credential secret itself is not returned to the attacker. This issue is fixed in version 3.1.4.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
29(Track)
EG Risk 29/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
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

September 12, 2026

Last Modified

September 15, 2026

Advisory Details (2)

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

Flowise before 3.1.4 Cross-Workspace Credential IDOR via node-load-method | Advisories | VulnCheck

https://www.vulncheck.com/advisories/flowise-before-3.1.4-cross-workspace-credential-idor-via-node-load-method
github Patch Available🟡 PoC Available

Cross-workspace credential IDOR in node-load-method allows low-privilege users to enumerate victim third-party resources · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-hqvm-7539-v83j

Vendor Advisories for CVE-2026-90534(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 / 31× 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-21 04:56 UTCEG score recompute
  2. 2026-09-21 04:56 UTCGHSA enrichment
  3. 2026-09-20 20:16 UTCEPSS rescore
  4. 2026-09-20 03:08 UTCEG score recompute
  5. 2026-09-20 03:08 UTCGHSA enrichment
  6. 2026-09-19 01:30 UTCEG score recompute
  7. 2026-09-19 01:30 UTCGHSA enrichment
  8. 2026-09-18 19:28 UTCEPSS rescore
  9. 2026-09-17 23:52 UTCEG score recompute
  10. 2026-09-17 23:52 UTCGHSA enrichment
  11. 2026-09-17 19:32 UTCEPSS rescore
  12. 2026-09-16 21:13 UTCEG score recompute
  13. 2026-09-16 21:13 UTCGHSA enrichment
  14. 2026-09-16 14:09 UTCEPSS rescore
  15. 2026-09-16 05:15 UTCEPSS rescore
  16. 2026-09-15 19:12 UTCEG score recompute▲ 0.40
  17. 2026-09-15 19:12 UTCGHSA enrichment
  18. 2026-09-15 19:12 UTCNVD updateCVSS v3 → 6.5
  19. 2026-09-15 03:12 UTCEPSS rescore
  20. 2026-09-14 21:18 UTCGHSA enrichment
  21. 2026-09-14 19:21 UTCEG score recompute
  22. 2026-09-14 19:21 UTCGHSA enrichment
  23. 2026-09-14 18:28 UTCEG score recompute
  24. 2026-09-14 18:28 UTCGHSA enrichment
  25. 2026-09-14 16:41 UTCEG score recompute
Show 6 more
  1. 2026-09-14 16:41 UTCGHSA enrichment
  2. 2026-09-13 16:48 UTCEPSS rescore
  3. 2026-09-13 15:03 UTCGHSA enrichment
  4. 2026-09-12 13:25 UTCEG score recompute
  5. 2026-09-12 12:19 UTCEG score recompute
  6. 2026-09-12 12:18 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-90534?
CVE-2026-90534 is a medium vulnerability published on September 12, 2026. Flowise is a low-code platform for building LLM applications. In versions up to and including 3.1.3, the POST /api/v1/node-load-method/:name endpoint is mounted without any route-level permission check and invokes component loadMethods with an attacker-controlled nodeName, loadMethod, inputs, and…
When was CVE-2026-90534 disclosed?
CVE-2026-90534 was first published in the National Vulnerability Database on September 12, 2026, with the most recent update 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-90534 actively exploited?
CVE-2026-90534 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 87.8% of all scored CVEs.
What is the CVSS score of CVE-2026-90534?
CVE-2026-90534 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-90534?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-90534, 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-90534

Explore →

Is Your Infrastructure Affected by CVE-2026-90534?

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

Start Free Scan →Browse All CVEs