{"answers":{"affected":"2 open source packages ship an affected version, including flowise. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-71338 exists.","fix":"No fix has been published for CVE-2025-71338 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-71338 is a critical path traversal vulnerability in Flowiseai Flowise, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-71338 and fix it if it is affected.\n\nWhat it is: CVE-2025-71338 is a critical path traversal vulnerability in Flowiseai Flowise, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-71338 exists.\n\nAffected packages and fixed versions:\n- flowise (npm): affected all versions up to 2.2.7; no fix listed\n- flowise (npm): affected all versions up to 2.2.7; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-71338/ (Markdown: https://insights.sbomify.com/CVE-2025-71338/index.md)","id":"CVE-2025-71338","markdown":"https://insights.sbomify.com/CVE-2025-71338/index.md","name":"CVE-2025-71338","record":{"aliases":["GHSA-8vvx-qvq9-5948","GHSA-c3hj-m5hq-59xw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Flowise AI application","requires_auth":"none","summary":"Unauthenticated attackers can exploit path traversal in the document-store API to write arbitrary files, leading to remote code execution.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"flowise","vendor":"flowiseai"}],"cvss":{"score":10,"severity":"critical","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-73","name":"External Control of File Name or Path"}],"description":"Flowise through 2.2.7 fails to sanitize path segments in the document-store loader endpoint, allowing unauthenticated attackers to write files outside the storage directory. Attackers can use parent-directory sequences to escape the storage directory and overwrite application files loaded at boot for remote code execution.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":"2026-08-03","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-08-03T09:50:19Z","kind":"github_poc","ref":"https://github.com/majpuV/flowise-arbitrary-file-read-getFileFromStorage","stars":0,"title":"Unauthenticated arbitrary file read in Flowise (\u003c 2.2.4) via path traversal in getFileFromStorage (storageUtils.ts). Caused by un-sanitized file path combined with mass-assignment in PUT /api/v1/document-store/store/:id. Allows full compromise via /root/.flowise/encryption.key read. Distinct from CVE-2025-71338 (fixed in 2.2.4)."}],"tier":"weaponised"},"has_fix":false,"headline":"Flowise through 2.2.7 - Arbitrary File Write to Remote Code Execution via document-store API","id":"CVE-2025-71338","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"flowiseai:flowise","products":["flowiseai:flowise"],"type":"path_traversal","year":"2025"},"n_packages":2,"n_references":3,"next":{"headline":"Picklescan - Arbitrary Code Execution via numpy.f2py.crackfortran._eval_length Gadget","id":"CVE-2025-71339"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["2.2.7"],"package":"flowise","purl":null,"source":"GHSA-8vvx-qvq9-5948"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["2.2.7"],"package":"flowise","purl":"pkg:npm/flowise","source":"GHSA-8vvx-qvq9-5948"}],"prev":{"headline":"Flowise - Unverified Email Change via Account Profile Endpoint","id":"CVE-2025-71337"},"products":["Flowise"],"published":"2026-06-25","related":[{"cvss_score":10,"headline":"Flowise: Authenticated RCE Via MCP Adapters","id":"CVE-2026-40933","kev_date_added":null,"published":"2026-04-21"},{"cvss_score":10,"headline":"Flowise is vulnerable to arbitrary file read, arbitrary file write","id":"CVE-2025-61913","kev_date_added":null,"published":"2025-10-08"},{"cvss_score":10,"headline":"Flowise has Remote Code Execution vulnerability","id":"CVE-2025-59528","kev_date_added":null,"published":"2025-09-22"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2026-52098","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":9.8,"headline":"Flowise Cloud and Local Deployments have Unauthenticated Password Reset Token Disclosure that Leads to Account Takeover","id":"CVE-2025-58434","kev_date_added":null,"published":"2025-09-12"},{"cvss_score":9.8,"headline":"Unsupervised OS command execution leads to remote code execution by unauthenticated network attackers","id":"CVE-2025-8943","kev_date_added":null,"published":"2025-08-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-17","vendors":["Flowise"]},"summary":"Unauthenticated attackers can exploit path traversal in the document-store API to write arbitrary files, leading to remote code execution.","url":"https://insights.sbomify.com/CVE-2025-71338/"}