Flowise through 3.1.4 Insecure Direct Object Reference via Credential (CVE-2026-100609) | HOL Guard CVE

High · CVSS 7.6CVE-2026-100609

Flowise through 3.1.4 Insecure Direct Object Reference via Credential

Answer in brief

CVE-2026-100609 records a High severity (CVSS 7.6) vulnerability in Flowise through 3.1.4 Insecure Direct Object Reference via Credential. The current sources do not mark it as known exploited. The current feed maps FlowiseAI/Flowise (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 26, 2026Updated Sep 26, 2026Source checked Sep 26, 2026First seen by HOL Sep 26, 2026Material review Sep 26, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.6
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

CVSS is 7.6. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps FlowiseAI/Flowise (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
FlowiseAI/Flowisegeneric	>=0 <=3.1.4	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for FlowiseAI/Flowise.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Sep 26, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 26, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 26, 2026

Sources and claim methodology

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.