Servers and applications
CVE-2026-30824
Missing Authentication on NVIDIA NIM Endpoints
- Severity
- High 7.7
- Published
- 5 Mar 2026
- Last changed
- 17 Jun 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 3.0.13
- Exploit chance
- 37% in the next 30 daysHigher than 98% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- Missing authentication (CWE-306)
- Attack
- Over the network · No login needed · No user action needed
- CVSS 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X- Also known as
- GHSA-5f53-522j-j454
- Sources
- NVD, Project advisories (GitHub)
Description
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.
In packages/server/src/utils/constants.ts, the NVIDIA NIM route is added to the authentication whitelist:
This causes the global auth middleware to skip authentication checks for all endpoints under /api/v1/nvidia-nim/*. None of the controller actions in packages/server/src/controllers/nvidia-nim/index.ts perform their own authentication checks.
The /get-token endpoint returns a valid NVIDIA API token without authentication. This token grants access to NVIDIA's inference API and can list 170+ LLM models.
On systems with Docker/NIM installed, an unauthenticated attacker can:
- List running containers (reconnaissance)
- Stop containers (Denial of Service)
- Start containers with arbitrary images
- Pull arbitrary Docker images (resource consumption, potential malicious images)
Affected software
| Software | Affected versions |
|---|---|
FlowiseServers and applications · cpe:a:flowiseai:flowise |
|
FlowiseServers and applications · github:flowiseai/flowise |
|
About Flowise
Build AI Agents, Visually
- Archived
- Yes, no longer maintainedGitHub
- Weekly downloads (npm)
- 6,604npm, 15 Nov 2026
- Docker Hub pulls
- 7,390,661Docker Hub, 15 Nov 2026
- GitHub stars
- 55,573GitHub, 15 Nov 2026
- Forks
- 25,094GitHub, 15 Nov 2026
- Latest release
- [email protected]GitHub, 15 Nov 2026
- Released
- 29 Jul 2026GitHub
- First published on GitHub
- 31 Mar 2023GitHub
Source code Website Docker image Package
Vulnerabilities in Flowise
- In our list
- 171
- Published in the last 12 months
- 149
- Critical, last 12 months
- 41
- High, last 12 months
- 70
- Known exploited
- 0
- CVE-2026-130796Flowise 3.1.3 through 3.1.4 MCP Server Token Disclosure via Public Chatflow EndpointHigh 8.8 17 Nov 2026
- CVE-2026-130615Flowise through 3.1.4 SSRF via DNS Rebinding in Playwright and Puppeteer LoadersHigh 7.6 17 Nov 2026
- CVE-2026-127214Flowise 3.1.4 SSRF Bypass via Custom Function SandboxMedium 6.3 13 Nov 2026
- CVE-2026-119978Flowise through 3.1.4 Custom Function Sandbox Escape RCE via LocalFileStoreCritical 9.0 30 Oct 2026
- CVE-2026-90580A vulnerability was found in FlowiseAI Flowise up to 3.0.2. This vulnerability affects the function axios.post of the file packages/server/src/controllers/evaluations/index.ts of the component Evaluations Endpoint. The manipulation of the argument Host/X-Forwarded-Proto results in server-side request forgery. The attack may be launched remotely. The exploit has been made public and could be…Low 2.1 13 Sept 2026
- CVE-2026-90535Flowise versions before 3.1.4 contain an unauthenticated denial of service vulnerability in the /api/v1/text-to-speech/abort endpoint that accepts user-supplied chatflowId and chatId without ownership verification. Attackers can terminate active chatflow predictions for any user by submitting requests with known chatflow and chat identifiers, causing targeted service disruption.Medium 6.3 12 Sept 2026
References
- NVD https://nvd.nist.gov/vuln/detail/CVE-2026-30824
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-30824
- GitHub Advisory Database https://github.com/advisories/GHSA-5f53-522j-j454
- github.com https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-5f53-522j-j454