Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.new Create a CVE report
Check your stack
CVE-2025-71334critical9.8

Flowise - Arbitrary File Access via Missing Chat Flow ID Validation

Impact

Flowise before version 3.0.6 has an arbitrary file access vulnerability due to missing validation of chatflowId and chatId parameters. An unauthenticated attacker can access files using certain endpoints. The impact is uncertain.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

Flowise · VulnCheck

Flowise

2 ranges
VulnCheck version evidence

Package identity

pkg:npm/flowiseExplore flowise →

Identity supplied by VulnCheck. Version matching requires compatible range evidence.

Compare with this publisher’s ranges. This does not inspect your installation.

affected

0 → before 3.0.6

semver versions

unaffected

3.0.6

semver versions

unknown

Other versions: unaffected

Original source description

Flowise before 3.0.6 contains an arbitrary file access vulnerability due to missing validation that the chatflowId and chatId parameters are UUIDs or numbers in file handling operations. By supplying a path-traversal value (e.g., '../../../../../tmp') as the chatflow id, an unauthenticated attacker can use the /api/v1/chatflows endpoint (via addBase64FilesToStorage) to write arbitrary files, and the /api/v1/get-upload-file and /api/v1/openai-assistants-file/download endpoints (via streamStorageFile) to read arbitrary files. Arbitrary file write may lead to remote code execution.

Inside the record

Evidence available

Package identity
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2025-71334

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-73 ↗

External Control of File Name or Path

VulnCheck

Related →

Environment requirements

These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.

VulnCheck · platform conditions

Any condition may hold

Vulnerable product

cpe:2.3:a:flowiseai:flowise:*:*:*:*:*:*:*:*

Before: 3.0.6

Original applicability statements
[
  {
    "nodes": [
      {
        "operator": "OR",
        "negate": false,
        "cpeMatch": [
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:a:flowiseai:flowise:*:*:*:*:*:*:*:*",
            "versionEndExcluding": "3.0.6"
          }
        ]
      }
    ]
  }
]
Contributing organizations · 2
VulnCheck

Assigning organization

2026-10-29
CISA-ADP

Additional data publisher

2026-06-26

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

4 sources
github.com/FlowiseAI/Flowise/security/advisories/GHSA-q67q-549q-p849
vendor-advisoryVulnCheck · CISA-ADP
github.com/FlowiseAI/Flowise/commit/8bd3de41533de78e4ef6c980e5704a1f9cb7ae6f
patchVulnCheck
github.com/FlowiseAI/Flowise/commit/c2b830f279e454e8b758da441016b2234f220ac7
patchVulnCheck
www.vulncheck.com/advisories/flowise-arbitrary-file-access-via-missing-chat-flow-id-validation
third-party-advisoryVulnCheck