{"answers":{"affected":"2 open source packages ship an affected version, including flowise. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-8182 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-8182 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-8182 is a high-severity denial of service vulnerability in Flowiseai Flowise, published on 27 Aug 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-8182 and fix it if it is affected.\n\nWhat it is: CVE-2024-8182 is a high-severity denial of service vulnerability in Flowiseai Flowise, published on 27 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-8182 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- flowise (npm): affected all versions up to 1.8.2; no fix listed\n- flowise (npm): affected all versions up to 1.8.2; 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-8182/ (Markdown: https://insights.sbomify.com/CVE-2024-8182/index.md)","id":"CVE-2024-8182","markdown":"https://insights.sbomify.com/CVE-2024-8182/index.md","name":"CVE-2024-8182","record":{"aliases":["GHSA-48x4-mx8f-gr4h"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Flowise AI platform","requires_auth":"none","summary":"Unauthenticated attackers can crash the Flowise instance by sending malicious input to the get-upload-file API endpoint.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"tenable","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:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"An Unauthenticated Denial of Service (DoS) vulnerability exists in Flowise version 1.8.2 leading to a complete crash of the instance running a vulnerable version due to improper handling of user supplied input to the “/api/v1/get-upload-file” api endpoint.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Flowise Denial of Service","id":"CVE-2024-8182","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"flowiseai:flowise","products":["flowiseai:flowise"],"type":"denial_of_service","year":"2024"},"n_packages":2,"n_references":1,"next":{"headline":"CORS Misconfiguration in prefecthq/prefect","id":"CVE-2024-8183"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.8.2"],"package":"flowise","purl":null,"source":"GHSA-48x4-mx8f-gr4h"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.8.2"],"package":"flowise","purl":"pkg:npm/flowise","source":"GHSA-48x4-mx8f-gr4h"}],"prev":{"headline":"Flowise Authentication Bypass","id":"CVE-2024-8181"},"products":["Flowise"],"published":"2024-08-27","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)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-27","vendors":["FlowiseAI"]},"summary":"Unauthenticated attackers can crash the Flowise instance by sending malicious input to the get-upload-file API endpoint.","url":"https://insights.sbomify.com/CVE-2024-8182/"}