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

Flowise: Broken Access Control in Stripe Subscription Endpoints Allows Cross-Tenant Billing Manipulation

FlowiseAI · Flowise

Official source article: GitHub GHSA-GMMW-QG98-6J6P ↗. Check the applicable product and release in the original source.

8.3HighCVSS 4.0
Recommended action
Within 7 days

High 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 severityHighOperational priority:Critical, raised one band.upgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.52% 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 3 daysRemediation target: Within 90 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.

Open-source package ranges1 source-attributed range

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
npmflowise<= 3.1.23.1.3GitHub advisory ↗upstream repository advisory · 4 Aug 2026
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-52872

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

High 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 is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, several organization billing endpoints in packages/server/src/enterprise/routes/organization.route.ts and packages/server/src/enterprise/controllers/organization.controller.ts accept attacker-controlled Stripe subscriptionId values without verifying that the identifier belongs to the authenticated user's organization. An authenticated attacker can perform unauthorized Stripe subscription operations on other tenants, including changing subscription plans or modifying seat quantities, resulting in financial impact and service disruption. This issue is fixed in 3.1.3.

What

Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, several organization billing endpoints in packages/server/src/enterprise/routes/organization.route.ts and packages/server/src/enterprise/controllers/organization.controller.ts accept attacker-controlled Stripe subscriptionId values without verifying that the identifier belongs to the authenticated user's organization. An authenticated attacker can perform unauthorized Stripe subscription operations on other tenants, including changing subscription plans or modifying seat quantities, resulting in financial impact and service disruption. This issue is fixed in 3.1.3.

Why

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, several organization billing endpoints in packages/server/src/enterprise/routes/organization.route.ts and packages/server/src/enterprise/controllers/organization.controller.ts accept attacker-controlled Stripe subscriptionId values without verifying that the identifier belongs to the authenticated user's organization. An authenticated attacker can perform unauthorized Stripe subscription operations on other tenants, including changing subscription plans or modifying seat quantities, resulting in financial impact and service disruption. This issue is fixed in 3.1.3.

Why

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

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 → Improper Access Control → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
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-284 ↗

CWE-284: Improper Access Control. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

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:N/UI:N/VC:N/VI:H/VA:L/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.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VIHighVulnerable-system integrity: A successful attack can cause a major loss.VALowVulnerable-system availability: A successful attack can cause a limited loss.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.
NetworkUnauthenticatedCWE-284Public exploit reference
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-2589Flowise: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Flowise ausnutzen, um beliebigen Code auszuführen – sogar mit Root-Rechten –, erweiterte Privilegien zu erlangen, Sicherheitsmaßnahmen zu umgehen, Sitzungen zu kapern sowie Daten offenzulegen oder zu manipulieren.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260805Security Bulletin 5 Aug 2026

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

Official advisory ↗
CSIRT Italia · Italian · aggiornamenti-di-sicurezza-per-flowiseAggiornamenti di sicurezza per Flowise

Sono stati recentemente resi pubblici diversi Proof of Concept (PoC) relativi a vulnerabilità che interessano la piattaforma Flowise riportati di seguito: CVE-2026-70476: la vulnerabilità potrebbe consentire la manipolazione non autorizzata di informazioni associate ai processi di billing e gestione delle risorse applicative. Un eventuale sfruttamento potrebbe compromettere l'integrità dei dati, alterare processi amministrativi e generare modifiche non autorizzate ai meccanismi di contabilizzazione delle risorse. CVE-2026-70474: la vulnerabilità interessa i meccanismi di autenticazione e autorizzazione basati su OAuth. Un attaccante potrebbe ottenere accessi non autorizzati a risorse e funzionalità applicative, con potenziale compromissione della riservatezza dei dati e delle identità digitali associate alla piattaforma. CVE-2026-70473: la vulnerabilità potrebbe consentire l'accesso non autorizzato a funzionalità e informazioni che dovrebbero risultare protette. Lo sfruttamento potrebbe permettere l'elusione di controlli applicativi e l'accesso non autorizzato a dati sensibili. CVE-2026-70470: la vulnerabilità potrebbe consentire l'esecuzione di operazioni non previste sui componenti vulnerabili della piattaforma. Un eventuale sfruttamento potrebbe compromettere l'integrità dell'ambiente applicativo e favorire attività ostili successive. CVE-2026-69264: la vulnerabilità interessa il componente CSVAgent e può consentire l'esecuzione di codice remoto attraverso l'iniezione di contenuto controllato dall'attaccante in codice Python eseguito tramite Pyodide. Un attaccante potrebbe eseguire comandi di sistema, accedere a file locali e compromettere completamente l'istanza vulnerabile. CVE-2026-69263: la vulnerabilità potrebbe consentire l’elusione di una precedente mitigazione relativa all'esecuzione di pacchetti tramite npx. Lo sfruttamento potrebbe permettere l'installazione e l'esecuzione non autorizzata di codice con i privilegi del processo Flowise, con conseguente compromissione del sistema. CVE-2026-69257: la vulnerabilità potrebbe consentire il bypass delle protezioni SSRF tramite indirizzi IPv4-mapped IPv6. Un attaccante potrebbe raggiungere servizi interni, endpoint cloud metadata o risorse normalmente non accessibili, con potenziale esposizione di credenziali, token e informazioni sensibili. CVE-2026-69256: la vulnerabilità interessa il nodo CSVAgent e consente l'esecuzione di codice arbitrario sfruttando la funzione pandas.read_pickle() per aggirare i controlli di sicurezza implementati. L'impatto può tradursi nella completa compromissione dell'istanza Flowise e nell'esecuzione di comandi arbitrari. CVE-2026-69255: la vulnerabilità potrebbe consentire l'esecuzione di codice arbitrario tramite iniezione di codice Python nel componente CSVAgent. Le evidenze pubblicate riportano l'ottenimento di una shell con privilegi elevati all'interno del container Flowise, con possibilità di accesso ai dati, esecuzione di comandi arbitrari e movimenti laterali verso ulteriori sistemi raggiungibili dall'host compromesso.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-033476flowiseaiのflowiseにおける複数の脆弱性

Flowiseは、カスタマイズされた大規模言語モデルのフローを構築するためのドラッグ＆ドロップユーザーインターフェースです。バージョン3.1.3以前のpackages/server/src/enterprise/routes/organization.route.tsおよびpackages/server/src/enterprise/controllers/organization.controller.tsの複数の組織向け請求エンドポイントでは、認証されたユーザーが組織に属しているかどうかを検証せずに、攻撃者が制御するStripeのsubscriptionIdの値を受け入れていました。認証された攻撃者は、他のテナントに対して未承認のStripeサブスクリプション操作（サブスクリプションプランの変更や座席数の変更など）を実行でき、その結果、金銭的な影響やサービスの中断が発生する可能性があります。この問題はバージョン3.1.3で修正されています。

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.2
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
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.
04

Evidence and provenance

Published 4 Aug 2026 · Last source change 5 Aug 2026, 14:51 UTC · CWE-284 · Improper Access Control

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-52872
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 patch: github.com/4d7899d02ca370a5510406be5c91483085a412f9; added patch: github.com/6321; 2 further additions.
    Before
    no authoritative guidance recorded
    After
    patch: github.com/4d7899d02ca370a5510406be5c91483085a412f9 · patch: github.com/6321 · remediation: github.com/6321 · 1 more references
    github.com ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 3.1.2 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    Flowise: < 3.1.2 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    CNA ↗
  3. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    github.com ↗
  4. 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-52872↗CISA Vulnrichment SSVC evidence↗Public exploit reference · GitHub GHSA-GMMW-QG98-6J6P↗Patch or update reference↗Patch or update reference↗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-70476 · cve.blacktree.nl