CVE-2026-30824 is a critical flaw (CVSS 9.8) in Flowise. Before version 3.0.13, the NVIDIA NIM router was whitelisted in the global authentication middleware, so its container management and token endpoints could be called without logging in. Upgrade to 3.0.13 and keep Flowise off open networks.
What's affected
The GitHub advisory lists Flowise up to and including 3.0.12 as affected and 3.0.13 as patched. The NVD text reads prior to 3.0.13. The package is flowise on npm, and container images based on older versions carry the same code.
The advisory scores its own severity as 8.6, while NVD scores the CVE 9.8. Both agree that no authentication was applied to the router at /api/v1/nvidia-nim/*.
How to check if you're exposed
Confirm your version first:
npm ls flowise
docker ps --format '{{.Image}}' | grep -i flowise
Then check exposure. Is your Flowise instance reachable from the internet or from networks you do not control? Look at your reverse proxy, load balancer and security group rules. If the host also runs Docker with NIM installed, the advisory says the container runtime could be affected, so check which containers are running and why.
What to do now
- Upgrade Flowise to 3.0.13 or later and redeploy.
- Restrict access to Flowise with network rules, a VPN or an authenticating proxy until the upgrade is done.
- Review running containers and pulled images on the host for anything you did not start.
- The advisory says one endpoint can return an NVIDIA API token. Rotate any NVIDIA tokens or keys configured in Flowise.
- Audit reverse proxy and application logs for calls to paths under
/api/v1/nvidia-nim/from unknown addresses.
Why it matters
The cause is a configuration list. The advisory points to a whitelist in constants.ts that tells the global authentication middleware which paths to skip. The NIM route was on it, and the controller actions did not check authentication themselves, so nothing protected them. The record files this under CWE-306, missing authentication for a critical function.
The advisory lists endpoints that could leak an API token, pull images, start or stop containers and list what is running. Impact depends on whether the host has Docker and NIM set up, but a leaked token is a problem on its own. A whitelist is an easy place for this mistake, because adding one path to it quietly removes protection from everything under it. The record does not mark this as exploited in the wild.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Why does NVD say 9.8 when the advisory says 8.6?
They use different scoring inputs. Treat it as critical until you have patched.
Do I need NIM installed to be affected?
The route exists in the affected Flowise versions regardless. The container impact depends on the host setup, but token exposure does not.
Sources
Last reviewed: 19 October 2026.
