{"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-2026-30824 exists.","fix":"Upgrade flowise to 3.0.13 or later.","what":"CVE-2026-30824 is a high-severity missing authorization vulnerability in Flowiseai Flowise, published on 7 Mar 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-2026-30824 and fix it if it is affected.\n\nWhat it is: CVE-2026-30824 is a high-severity missing authorization vulnerability in Flowiseai Flowise, published on 7 Mar 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-2026-30824 exists.\n\nAffected packages and fixed versions:\n- flowise (npm): affected all versions; fixed in 3.0.13\n- flowise (npm): affected all versions; fixed in 3.0.13\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-2026-30824/ (Markdown: https://insights.sbomify.com/CVE-2026-30824/index.md)","id":"CVE-2026-30824","markdown":"https://insights.sbomify.com/CVE-2026-30824/index.md","name":"CVE-2026-30824","record":{"aliases":["GHSA-5f53-522j-j454"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"LLM flow builder","requires_auth":"none","summary":"Unauthenticated attackers can access privileged NVIDIA NIM endpoints to manage containers and generate tokens in Flowise.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"flowise","vendor":"flowiseai"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"Flowise is a drag \u0026 drop user interface to build a customized large language model flow. Prior to version 3.0.13, the NVIDIA NIM router (/api/v1/nvidia-nim/*) is whitelisted in the global authentication middleware, allowing unauthenticated access to privileged container management and token generation endpoints. This issue has been patched in version 3.0.13.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":"2026-04-29","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":1,"refs":[{"date":"2026-04-29T16:18:01Z","kind":"github_poc","ref":"https://github.com/dylvie/CVE-2026-30824-Flowise-NVIDIA-NIM-Authentication","stars":0,"title":"A proof-of-concept exploit for **CVE-2026-30824**, a critical authentication bypass vulnerability in Flowise that exposes NVIDIA NIM API endpoints without authentication."},{"date":null,"kind":"nuclei","ref":"http/cves/2026/CVE-2026-30824.yaml","stars":null,"title":"Flowise - NVIDIA NIM Endpoints Missing Authentication"}],"tier":"weaponised"},"has_fix":true,"headline":"Flowise: Missing Authentication on NVIDIA NIM Endpoints","id":"CVE-2026-30824","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"flowiseai:flowise","products":["flowiseai:flowise"],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"hoppscotch: IDOR - Any authenticated user can revoke any other user's Personal Access Token","id":"CVE-2026-30825"},"packages":[{"ecosystem":"npm","fixed":["3.0.13"],"introduced":["0"],"last_affected":[],"package":"flowise","purl":null,"source":"GHSA-5f53-522j-j454"},{"ecosystem":"npm","fixed":["3.0.13"],"introduced":["0"],"last_affected":[],"package":"flowise","purl":"pkg:npm/flowise","source":"GHSA-5f53-522j-j454"}],"prev":{"headline":"Flowise: IDOR leading to Account Takeover and Enterprise Feature Bypass via SSO Configuration","id":"CVE-2026-30823"},"products":["Flowise"],"published":"2026-03-07","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":"partial"},"state":"PUBLISHED","updated":"2026-03-09","vendors":["FlowiseAI"]},"summary":"Unauthenticated attackers can access privileged NVIDIA NIM endpoints to manage containers and generate tokens in Flowise.","url":"https://insights.sbomify.com/CVE-2026-30824/"}