CVE-2026-30824

Flowise, an open-source drag-and-drop interface for building LLM flows, whitelists its NVIDIA NIM router (/api/v1/nvidia-nim/*) in the global authentication middleware, so requests to these endpoints bypass authentication entirely (CWE-306). An unauthenticated attacker with network access to a vulnerable Flowise instance can simply send HTTP requests to the NVIDIA NIM router and reach privileged container management and token generation functionality. Successful abuse does not directly compromise the Flowise process itself, but gives the attacker privileged control over container management and token issuance, which carries high impact on the downstream/connected NVIDIA NIM infrastructure (CVSS 4.0 subsequent-system impact: high). All Flowise deployments running a version prior to 3.0.13 are affected, particularly self-hosted instances exposed to the internet or to untrusted networks. The flaw is fixed in 3.0.13; it is not yet in CISA's KEV catalog, but a public advisory (GHSA-5f53-522j-j454) exists and EPSS assigns a 36.3% probability of exploitation within 30 days (98th percentile), indicating elevated near-term risk.

What to do: Upgrade Flowise to version 3.0.13 or later, which removes the NVIDIA NIM router from the authentication whitelist. Until patched, restrict network exposure of the /api/v1/nvidia-nim/* path (e.g., require authentication at a reverse proxy) and avoid exposing Flowise directly to the internet. Administrators should also review for unexpected containers or changes and rotate any tokens that could have been issued through the unauthenticated endpoint.