Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2025-71324 – Unauthenticated Arbitrary File Read (Path Traversal) – Flowise before 3.0.6

Be the first to know when new zero-days emerge:

Summary

CVE-2025-71324 is a high-severity unauthenticated path traversal vulnerability in Flowise, the open-source AI agent and LLM workflow builder, affecting all versions prior to 3.0.6. By supplying crafted path traversal sequences in the unvalidated chatId parameter, a remote unauthenticated attacker can read arbitrary files from the server filesystem — including the default SQLite database — without any credentials. The vulnerability is tracked under GitHub Security Advisory GHSA-99pg-hqvx-r4gf and carries a CVSS 4.0 score of 8.7 (High).

Technical details

  • Root cause: The streamStorageFile() function, invoked by two API endpoints, validates the chatflowId parameter (enforcing UUID format) and sanitizes fileName, but performs no validation whatsoever on the chatId parameter. When the target file is not found at the initial path (which includes orgId), the function falls back to a secondary path constructed without orgId. This fallback is evaluated after the storage-directory containment check, meaning path traversal sequences (e.g., ../.././) in chatId successfully escape the intended storage boundary.
  • Trigger conditions: No authentication is required. The only prerequisite is a reachable Flowise instance. A valid chatflowId UUID can be independently leaked from the same instance via verbose error messages returned by the /api/v1/vector/upsert/ endpoint.
  • Attack vector: Remote, over the network, via crafted HTTP GET requests to either vulnerable endpoint — no user interaction needed.
  • Affected endpoints:
    • /api/v1/get-upload-file
    • /api/v1/openai-assistants-file/download
  • Impact: High-severity confidentiality breach. In the default Flowise configuration, attackers can read /root/.flowise/database.sqlite, exposing the entire database including all stored API keys. Those API keys can subsequently be used to gain full administrative access to the Flowise instance and any integrated systems.

Affected software

  • Flowise — all versions up to and including 3.0.5

Severity

  • CVSS 4.0: 8.7 — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
  • CVSS v3.1: 9.1 — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Mitigation and recommended actions

  • Immediate: Upgrade Flowise to version 3.0.6 or later, which contains the vendor-provided fix for this vulnerability.
  • If immediate patching is not feasible:
    • Restrict network access to the Flowise instance — place it behind a reverse proxy or firewall that limits access to trusted IP ranges only.
    • Disable or block unauthenticated access to the /api/v1/get-upload-file and /api/v1/openai-assistants-file/download endpoints at the network perimeter.
    • Rotate all API keys stored in the Flowise database, as prior exposure cannot be ruled out on unpatched instances.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge