Quick answers
- Is CVE-2025-71338 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-71338 being exploited in the wild.
- How severe is CVE-2025-71338?
- Critical severity, with a CVSS score of 10, published 25 June 2026.
- Which products and versions are affected?
- flowise (npm) <= 2.2.7, SEMVER:introduced=0,last_affected=2.2.7.
- Is there a fix for CVE-2025-71338?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2025-71338 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2025-71338?
- Check whether you run flowise (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A path traversal vulnerability exists in the `/api/v1/document-store/loader/process` endpoint of Flowise. The root cause is the lack of sanitization of the `fileName` parameter within the `storageUtils.ts` component, specifically in functions like `addBase64FilesToStorage`. An unauthenticated attacker can use `../` sequences in the `txtFile` parameter to escape the intended directory and overwrite arbitrary files on the host. A demonstrated exploit involves overwriting `package.json` to modify the application's start scripts, resulting in Remote Code Execution (RCE) when the service is restarted. As of the advisory date, no patched version is specified, though the vulnerability is confirmed in version 1.8.2.
Affected products
- FlowiseAI Flowise <= 1.8.2
Identifiers
- CVE-2025-71338
- GHSA-8vvx-qvq9-5948
Timeline
- 2025-03-14: advisory: GitHub Security Advisory published
- 2026-06-25: disclosed: NVD publication date