{"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-26319 exists.","fix":"No fix has been published for CVE-2025-26319 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-26319 is a critical vulnerability in Flowiseai Flowise, published on 4 Mar 2025. 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-26319 and fix it if it is affected.\n\nWhat it is: CVE-2025-26319 is a critical vulnerability in Flowiseai Flowise, published on 4 Mar 2025. 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-26319 exists.\n\nAffected packages and fixed versions:\n- flowise (npm): affected all versions up to 2.2.6; no fix listed\n- flowise (npm): affected all versions up to 2.2.6; 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-26319/ (Markdown: https://insights.sbomify.com/CVE-2025-26319/index.md)","id":"CVE-2025-26319","markdown":"https://insights.sbomify.com/CVE-2025-26319/index.md","name":"CVE-2025-26319","record":{"aliases":["GHSA-69jq-qr7w-j7qh"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"FlowiseAI Flowise","requires_auth":"none","summary":"Attackers can upload arbitrary files via the attachments API, potentially leading to remote code execution in FlowiseAI Flowise.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"flowise","vendor":"flowiseai"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"FlowiseAI Flowise v2.2.6 was discovered to contain an arbitrary file upload vulnerability in /api/v1/attachments.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":"2025-02-02","github_poc":2,"max_poc_stars":0,"metasploit":0,"nuclei":1,"refs":[{"date":"2025-02-02T08:02:48Z","kind":"github_poc","ref":"https://github.com/dorattias/CVE-2025-26319","stars":0,"title":null},{"date":"2025-03-14T00:05:24Z","kind":"github_poc","ref":"https://github.com/redpack-kr/CVE-2025-26319","stars":0,"title":null},{"date":null,"kind":"nuclei","ref":"http/cves/2025/CVE-2025-26319.yaml","stars":null,"title":"FlowiseAI Flowise \u003c= 2.2.6 - Arbitrary File Upload"}],"tier":"weaponised"},"has_fix":false,"headline":"FlowiseAI Flowise arbitrary file upload vulnerability","id":"CVE-2025-26319","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"flowiseai:flowise","products":["flowiseai:flowise"],"type":"file_upload","year":"2025"},"n_packages":2,"n_references":1,"next":{"headline":"Command injection in n/a","id":"CVE-2025-26320"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["2.2.6"],"package":"flowise","purl":null,"source":"GHSA-69jq-qr7w-j7qh"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["2.2.6"],"package":"flowise","purl":"pkg:npm/flowise","source":"GHSA-69jq-qr7w-j7qh"}],"prev":{"headline":"Information disclosure in TSplus Remote Access","id":"CVE-2025-26318"},"products":["n/a"],"published":"2025-03-04","related":[{"cvss_score":10,"headline":"Flowise through 2.2.7 - Arbitrary File Write to Remote Code Execution via document-store API","id":"CVE-2025-71338","kev_date_added":null,"published":"2026-06-25"},{"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":"attribution","licence":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-05","vendors":["n/a"]},"summary":"Attackers can upload arbitrary files via the attachments API, potentially leading to remote code execution in FlowiseAI Flowise.","url":"https://insights.sbomify.com/CVE-2025-26319/"}