{"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-2024-36420 exists.","fix":"No fix has been published for CVE-2024-36420 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-36420 is a high-severity path traversal vulnerability in Flowiseai Flowise, published on 1 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-36420 and fix it if it is affected.\n\nWhat it is: CVE-2024-36420 is a high-severity path traversal vulnerability in Flowiseai Flowise, published on 1 Jul 2024. 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-2024-36420 exists.\n\nAffected packages and fixed versions:\n- flowise (npm): affected all versions up to 1.4.3; no fix listed\n- flowise (npm): affected all versions up to 1.4.3; 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-2024-36420/ (Markdown: https://insights.sbomify.com/CVE-2024-36420/index.md)","id":"CVE-2024-36420","markdown":"https://insights.sbomify.com/CVE-2024-36420/index.md","name":"CVE-2024-36420","record":{"aliases":["GHSA-h997-3fxj-p5j8"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Flowise LLM UI","requires_auth":"none","summary":"Attackers can read arbitrary files from the server via the openai-assistants-file endpoint due to unsanitized input in Flowise.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"flowise","vendor":"flowiseai"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"Flowise is a drag \u0026 drop user interface to build a customized large language model flow. In version 1.4.3 of Flowise, the `/api/v1/openai-assistants-file` endpoint in `index.ts` is vulnerable to arbitrary file read due to lack of sanitization of the `fileName` body parameter. No known patches for this issue are available.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":"2026-05-19","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":1,"refs":[{"date":"2026-05-19T06:56:35Z","kind":"github_poc","ref":"https://github.com/fineman999/POC_CVE-2024-36420","stars":0,"title":"POC_CVE-2024-36420"},{"date":null,"kind":"nuclei","ref":"http/cves/2024/CVE-2024-36420.yaml","stars":null,"title":"Flowise 1.4.3 - Arbitrary File Read"}],"tier":"weaponised"},"has_fix":false,"headline":"GHSL-2023-232: Flowise Path Injection at /api/v1/openai-assistants-file","id":"CVE-2024-36420","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"flowiseai:flowise","products":["flowiseai:flowise"],"type":"path_traversal","year":"2024"},"n_packages":2,"n_references":2,"next":{"headline":"GHSL-2023-234: Flowise Cors Misconfiguration in packages/server/src/index.ts","id":"CVE-2024-36421"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.4.3"],"package":"flowise","purl":null,"source":"GHSA-h997-3fxj-p5j8"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.4.3"],"package":"flowise","purl":"pkg:npm/flowise","source":"GHSA-h997-3fxj-p5j8"}],"prev":{"headline":"SuiteCRM-Core Host Header Injection in /legacy","id":"CVE-2024-36419"},"products":["Flowise"],"published":"2024-07-01","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["FlowiseAI"]},"summary":"Attackers can read arbitrary files from the server via the openai-assistants-file endpoint due to unsanitized input in Flowise.","url":"https://insights.sbomify.com/CVE-2024-36420/"}