Security readout for executives and security teams
Plain-English summary
Flowise has a critical flaw that may let an unauthenticated remote attacker write files on the server. Changing sensitive application files can lead to remote code execution when Flowise restarts. Treat internet-exposed Flowise deployments as urgent, but active exploitation is not confirmed by the provided sources.
Executive priority
Make this an immediate priority for any internet-facing Flowise deployment. The business risk is full server compromise, not just data exposure. If Flowise is internal-only and tightly segmented, urgency is lower but still high until vendor remediation status is confirmed.
Technical view
CVE-2025-71338 is a CWE-73 path traversal issue in Flowise’s /api/v1/document-store/loader/process endpoint. Unsanitized fileName handling enables arbitrary file write. The source bundle reports CVSS 4.0 score 10.0 and possible RCE via overwritten application files after restart. Exact affected version range and fixed version are not provided.
Likely exposure
Highest risk applies to Flowise instances whose API is reachable from untrusted networks. The issue is reported as unauthenticated and network-exploitable. The source bundle lists Flowise as affected but does not provide a clear version range beyond the supplied affected entry, so asset inventory and vendor advisory checks are necessary.
Exploitation context
The CVE is not listed as KEV, and the provided sources do not state active exploitation. Reported exploitation conditions are severe: remote network access, low complexity, no privileges, and no user interaction. RCE depends on attacker-controlled file writes affecting files used by the application during restart.
Researcher notes
Evidence is limited to the CVE bundle, GitHub advisory reference, and VulnCheck advisory reference. The bundle does not name a fixed version or confirmed exploit activity. Avoid assuming all versions are affected beyond the provided Flowise affected entry; verify directly against vendor advisory updates.
Mitigation direction
- Identify all Flowise deployments and remove public access until vendor remediation is confirmed.
- Restrict the affected document-store API route to trusted networks where possible.
- Check the Flowise GitHub advisory and VulnCheck advisory for fixed versions or vendor guidance.
- Upgrade or apply vendor-recommended remediation when confirmed by Flowise.
- Run Flowise with least filesystem privileges and limit write access to application paths.
Validation and detection
- Inventory Flowise instances, owners, network exposure, and deployed versions.
- Check whether the document-store API is reachable from untrusted networks.
- Review Flowise logs for suspicious document-store loader activity or unexpected file write errors.
- Inspect application directories for unexpected changes to critical files.
- Confirm remediation status against Flowise’s security advisory before reopening external access.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
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.
Open ATT&CK lookupCVE-2025-71338 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 10 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H3.96VulnCheckVulnerability scoring details
Base CVSS 4.0 score
10CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-8vvx-qvq9-5948)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: Flowise - Arbitrary File Write to Remote Code Execution via document-store APICVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.