CVE-2025-71324: Flowise - Arbitrary File Read via chatId Parameter
Flowise before 3.0.6 contains an arbitrary file read vulnerability in the chatId parameter of the /api/v1/get-upload-file and /api/v1/openai-assistants-file/download endpoints. The chatId value is not validated and is passed to streamStorageFile(), where a fallback file-lookup path constructed without the orgId is evaluated after the storage-directory containment check, allowing path traversal beyond the intended storage directory. Unauthenticated attackers can read sensitive files such as /root/.flowise/database.sqlite, exposing all database content in the default configuration.
Security readout for executives and security teams
Plain-English summary
Flowise deployments before 3.0.6 can let an unauthenticated remote attacker read files from the server. In default setups, this can expose the Flowise SQLite database, which may contain sensitive application data. The issue is high urgency where Flowise is internet-facing or handles customer, credential, or workflow data.
Executive priority
Prioritize remediation this week, or immediately for internet-facing Flowise. The business risk is sensitive data disclosure without login, not service disruption or code execution based on the provided evidence.
Technical view
The chatId parameter in two Flowise file-download endpoints is not validated before reaching streamStorageFile(). A fallback lookup path without orgId is evaluated after the storage containment check, enabling path traversal outside the intended storage directory. The reported impact is confidentiality loss only.
Likely exposure
Exposure is most likely in Flowise instances before 3.0.6, especially publicly reachable deployments using default local storage and SQLite paths. Internal-only instances still carry risk from unauthenticated network access.
Exploitation context
The source bundle does not cite active exploitation, and KEV status is false. The vulnerability is remotely reachable, requires no authentication, and has low attack complexity according to CVSS 4.0 scoring.
Researcher notes
Evidence supports CWE-73 external control of file path. The affected endpoints are /api/v1/get-upload-file and /api/v1/openai-assistants-file/download. Avoid assuming broader product impact beyond Flowise before 3.0.6.
Mitigation direction
Upgrade Flowise to version 3.0.6 or later.
Restrict network access to Flowise until the upgrade is complete.
Review vendor advisory guidance for configuration-specific mitigations.
Check whether sensitive data in Flowise storage or SQLite may be exposed.
Rotate affected secrets if database or configuration exposure is suspected.
Validation and detection
Inventory all Flowise deployments and confirm their running version.
Check whether the affected endpoints are reachable without authentication.
Review access logs for unusual file-download endpoint activity.
Confirm upgraded systems no longer accept traversal-style chatId values.
Assess whether default SQLite storage exists on affected hosts.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-73: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-73 · source CWE mapping
External Control of File Name or Path
External Control of File Name or Path represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.