BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-73488High confidence

Flowise before 3.1.3 IDOR via customer-default-source endpoint

FlowiseAI · Flowise

Official source article: GitHub GHSA-2364-JH4Q-M9VM ↗. Check the applicable product and release in the original source.

6.0MediumCVSS 4.0
Recommended action
Within 7 days

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:High, raised one band.upgradedsince 13 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • EPSS is 0.37% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs FlowiseAI Flowise and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-57804

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

Flowise versions before 3.1.3 contain an insecure direct object reference vulnerability in the GET /api/v1/organization/customer-default-source endpoint that allows authenticated attackers to access other customers' payment and profile data by manipulating the customerId parameter. Attackers can enumerate predictable customer IDs to retrieve sensitive information including email addresses, account balances, currency types, and billing configurations without authorization checks.

What

Flowise versions before 3.1.3 contain an insecure direct object reference vulnerability in the GET /api/v1/organization/customer-default-source endpoint that allows authenticated attackers to access other customers' payment and profile data by manipulating the customerId parameter. Attackers can enumerate predictable customer IDs to retrieve sensitive information including email addresses, account balances, currency types, and billing configurations without authorization checks.

Why

The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may obtain information outside the intended access boundary.

What

Flowise versions before 3.1.3 contain an insecure direct object reference vulnerability in the GET /api/v1/organization/customer-default-source endpoint that allows authenticated attackers to access other customers' payment and profile data by manipulating the customerId parameter. Attackers can enumerate predictable customer IDs to retrieve sensitive information including email addresses, account balances, currency types, and billing configurations without authorization checks.

Why

The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may obtain information outside the intended access boundary.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Authorization Bypass Through User-Controlled Key → obtain information outside the intended access boundary
Attack surface
Network
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-639 ↗

CWE-639: Authorization Bypass Through User-Controlled Key. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkCWE-639Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Cyber Security Agency of Singapore · English · CSA-SB-20260819Security Bulletin 19 Aug 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 19 Aug 2026, published on 19 August 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CSIRT Italia · Italian · flowise-disponibili-poc-per-lo-sfruttamento-di-nuove-vulnerabilitaFlowise: disponibili PoC per lo sfruttamento di nuove vulnerabilità

Sono stati recentemente resi pubblici diversi Proof of Concept (PoC) relativi a vulnerabilità che interessano la piattaforma Flowise. Di seguito i dettagli: CVE-2026-73483 : la vulnerabilità - di tipo " OS Command Injection " e con score CVSS v4.0 pari 9.4 - interessa il "Custom Function Node" di Flowise, esposto tramite l'endpoint /api/v1/node-custom-function , che utilizza la sandbox JavaScript vm2/@flowiseai/nodevm . Un utente malevolo autenticato, con accesso all'endpoint /api/v1/node-custom-function può fornire valori appositamente predisposti nei parametri " executablePath " e " args" utilizzati dalla funzione puppeteer.launch() , inducendo l'applicazione ad avviare processi controllati dall'attaccante al di fuori della sandbox vm2. Tale vulnerabilità, consente di aggirare i meccanismi di isolamento della sandbox ed eseguire codice arbitrario sul sistema che ospita Flowise; CVE-2026-73484 : la vulnerabilità - di tipo “Incomplete List of Disallowed Inputs” e con score CVSS v4.0 pari a 8.6 - interessa il componente “CSVAgent” di Flowise e, in particolare, il meccanismo di validazione del codice Python implementato nel modulo pythonCodeValidator.ts . La vulnerabilità è causata da controlli di sicurezza insufficienti all'interno della sandbox Pyodide: la denylist non include alcuni metodi nativi di Pandas, quali to_csv() , to_json() , query() e pipe() . Un utente malevolo autenticato, che riesce a interagire con “CSVAgent”, può fornire input appositamente predisposti per indurre il modello a generare codice Python contenente tali metodi, aggirando i controlli della sandbox Pyodide . Tale vulnerabilità, qualora sfruttata, consente di esfiltrare dati elaborati dal “CSVAgent” e di scrivere file arbitrari sul filesystem del sistema che ospita Flowise; CVE-2026-73485 : la vulnerabilità - di tipo "Code Injection" e con score CVSS v4.0 pari a 9.0 - interessa il nodo “Airtable Agent” di Flowise ed è dovuta alla modalità di validazione del codice Python generato dal modello, prima della sua esecuzione tramite Pyodide . Un utente malevolo potrebbe inviare input appositamente predisposti ad un chatflow che utilizza il nodo “Airtable Agent”, inducendo il modello a generare codice Python malevolo. Tale vulnerabilità consente di eludere i meccanismi di sicurezza previsti per la validazione del codice ed eseguire codice arbitrario sul sistema che ospita Flowise con i privilegi dell'utente che esegue il servizio; CVE-2026-73486 : la vulnerabilità - di tipo "Code Injection" e con score CVSS v4.0 pari a 9.0 - interessa il nodo “CSVAgent” di Flowise e, in particolare, il parametro customReadCSV , il cui valore viene utilizzato per costruire ed eseguire codice Python tramite Pyodide . La vulnerabilità è causata da un'insufficiente validazione dell'input: un utente malevolo autenticato può fornire un valore appositamente predisposto nel parametro customReadCSV , inducendo l'applicazione ad eseguire codice Python ed eludendo i controlli di sicurezza previsti. Tale vulnerabilità consente di aggirare i meccanismi di validazione del codice ed eseguire codice arbitrario sul sistema che ospita Flowise con i privilegi dell'utente che esegue il servizio; CVE-2026-73487 : la vulnerabilità - di tipo "Code Injection" e con score CVSS v4.0 pari a 9.0 - interessa i nodi “CSVAgent” e “Airtable Agent” di Flowise, che utilizzano la funzione validatePythonCodeForDataFrame() per validare il codice Python generato dal modello. La vulnerabilità è causata da inadeguati controlli di sicurezza dell'input: un utente malevolo non autenticato può inviare input appositamente predisposti all'endpoint /api/v1/prediction/:id , inducendo l'applicazione a generare ed eseguire codice Python che aggira i controlli di sicurezza basati su una blocklist incompleta. Tale vulnerabilità consente di esfiltrare dati sensibili e di effettuare attacchi di tipo “Server-Side Request Forgery (SSRF)” verso risorse interne; CVE-2026-73488 : la vulnerabilità - di tipo "Authorization Bypass" e con score CVSS v4.0 pari a 6.0 - interessa l'endpoint /api/v1/organization/customer-default-source di Flowise. La vulnerabilità è causata dall'assenza di adeguati controlli di autorizzazione sul parametro customerId , il cui valore viene utilizzato senza verificare che l'utente richiedente sia autorizzato ad accedere alle informazioni associate. Un utente malevolo autenticato può modificare il valore del parametro customerId all'interno della richiesta HTTP e ottenere informazioni riferite ad altri utenti. Tale vulnerabilità consente di accedere a dati sensibili di terzi, inclusi indirizzi e-mail, informazioni di fatturazione, saldi degli account e configurazioni di pagamento; CVE-2026-73601 : la vulnerabilità - di tipo "Eval Injection" e con score CVSS v4.0 pari a 9.0 - interessa il nodo “Custom MCP” di Flowise quando è abilitato il protocollo StdioClientTransport tramite l'impostazione CUSTOM_MCP_PROTOCOL=stdio . La vulnerabilità è causata da controlli insufficienti sui parametri di configurazione e sulle variabili d'ambiente utilizzate per avviare nuovi processi. Un utente malevolo autenticato può fornire una configurazione “Custom MCP” appositamente predisposta, inducendo l'applicazione ad eseguire comandi arbitrari sul sistema attraverso processi node o python3 ; CVE-2026-73602 : la vulnerabilità - di tipo "Eval Injection" e con score CVSS v4.0 pari a 9.0 - interessa i componenti “Custom Function Agent” e “Custom Tool” di Flowise, che utilizzano la sandbox FlowiseAI/nodevm basata su vm2 per l'esecuzione di codice JavaScript. La vulnerabilità è causata dall'utilizzo di una versione vulnerabile di vm2 , che consente di aggirare i meccanismi di isolamento della sandbox ed eseguire codice al di fuori dell'ambiente ristretto previsto. Un utente malevolo autenticato può fornire codice JavaScript appositamente predisposto, ottenendo l'evasione dalla sandbox e l'esecuzione di comandi sul sistema sottostante; CVE-2026-73603 : la vulnerabilità - di tipo "Missing Authorization" e con score CVSS v4.0 pari a 6.3 - interessa l'endpoint /api/v1/text-to-speech/generate di Flowise, esposto senza autenticazione e utilizzato per la generazione audio tramite servizi Text-to-Speech. La vulnerabilità è causata dall'assenza di controlli che verifichino se il chatflowId fornito appartenga ad un chatflow pubblico prima di utilizzare le relative credenziali TTS. Un utente malevolo può inviare richieste appositamente predisposte all'endpoint specificando l'identificativo di un chatflow valido, inducendo l'applicazione ad utilizzare le credenziali OpenAI o ElevenLabs associate a tale chatflow. Tale vulnerabilità consente di abusare delle credenziali TTS di altri utenti, generare contenuti audio non autorizzati e causare consumo di quote e costi a carico del proprietario del chatflow; CVE-2026-73604 : la vulnerabilità - di tipo "Information Disclosure" e con score CVSS pari a 6.5 - interessa l'endpoint /api/v1/credentials/:id di Flowise, utilizzato per recuperare le credenziali memorizzate dall'applicazione. La vulnerabilità è causata da un meccanismo di redazione incompleto che maschera esclusivamente i campi definiti come password, esponendo invece in chiaro informazioni sensibili memorizzate in campi di tipo string . Un utente malevolo autenticato con permessi di visualizzazione delle credenziali può interrogare l'endpoint e ottenere segreti applicativi, quali stringhe di connessione a database, chiavi di accesso cloud e credenziali di servizi esterni.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-031955flowiseaiのflowiseにおけるユーザ制御の鍵による認証回避に関する脆弱性

Flowiseのバージョン3.1.3未満には、GET /api/v1/organization/customer-default-sourceエンドポイントにおいて、不適切な直接オブジェクト参照の脆弱性が存在します。この脆弱性により、認証済みの攻撃者はcustomerIdパラメータを操作して他の顧客の支払い情報やプロフィールデータにアクセスできます。攻撃者は予測可能な顧客IDを列挙し、メールアドレス、アカウント残高、通貨種類、請求設定などの機微な情報を認可チェックなしに取得することが可能です。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Flowise: < 3.1.3
Fixed
Flowise: 3.1.3
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
Official vendor articles1 stored document

Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.

04

Evidence and provenance

Published 13 Aug 2026 · Last source change 13 Aug 2026, 14:51 UTC · CWE-639 · Authorization Bypass Through User-Controlled Key

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-57804
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: github.com/GHSA-2364-jh4q-m9vm.
    Before
    remediation: github.com/GHSA-2364-jh4q-m9vm
    After
    remediation: github.com/GHSA-2364-jh4q-m9vm · vendor advisory: github.com/GHSA-2364-jh4q-m9vm
    github.com ↗
  2. Public exploit evidencePublic exploit evidence changed from Public exploit reference to Public exploit reference.
    Before
    Public exploit reference
    After
    Public exploit reference
    github.com ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-57804↗CISA Vulnrichment SSVC evidence↗Public exploit reference · GitHub GHSA-2364-JH4Q-M9VM↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-73488 · cve.blacktree.nl