← Back to the live CVE advisory feed

CVE-2026-90534: Product identification pending

Severity

6.1 (MEDIUM)

Affected versions

up to and including 3

Fixed version

3.1.4.

Patch status

Patched

Published

2026-09-12T13:16:51.247

Modified

2026-09-12T13:16:51.247

Why it matters

Vulnerability requiring standard triage and vendor validation.

Recommended admin actions

• Review during normal vulnerability triage unless the affected system is internet-facing or business-critical.

Technical summary

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.

View the official NVD record for CVE-2026-90534

CVE data is sourced from NVD/CNA records and optional enrichment. Validate against the vendor advisory before taking production action.