CVE-2026-30824: CWE-306: Missing Authentication for Critical Function in FlowiseAI Flowise
Flowise is a drag & 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.
AI Analysis
Technical Summary
CVE-2026-30824 is a vulnerability classified under CWE-306 (Missing Authentication for Critical Function) affecting FlowiseAI's Flowise product versions prior to 3.0.13. Flowise is a drag-and-drop interface designed to build customized large language model workflows. The vulnerability arises because the NVIDIA NIM router endpoints under the path /api/v1/nvidia-nim/* are globally whitelisted in the authentication middleware, effectively bypassing authentication controls. This misconfiguration allows any unauthenticated user to access sensitive API endpoints responsible for container management and token generation. These endpoints are critical as they control privileged operations within containerized environments and manage authentication tokens, which could be leveraged to escalate privileges or manipulate system behavior. The vulnerability is remotely exploitable over the network without requiring any user interaction or prior authentication, increasing its risk profile. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N) reflects that the attack complexity is low, no privileges or user interaction are needed, and the scope is high due to the potential to affect multiple components or containers. The flaw was addressed and patched in Flowise version 3.0.13 by removing the global whitelist and enforcing proper authentication on the affected endpoints. No public exploits have been reported yet, but the nature of the vulnerability makes it a critical concern for organizations deploying vulnerable versions.
Potential Impact
The impact of CVE-2026-30824 is significant for organizations using Flowise versions prior to 3.0.13, especially those leveraging the NVIDIA NIM router for container orchestration and token management. Exploitation could allow attackers to gain unauthorized access to privileged container management functions, potentially leading to container manipulation, unauthorized deployment or termination of containers, and unauthorized token generation. This could result in unauthorized access to sensitive data, disruption of AI workflows, and compromise of the integrity and availability of AI services. Since the vulnerability requires no authentication or user interaction, it can be exploited remotely by any attacker with network access to the vulnerable API endpoints. This broadens the attack surface and increases the likelihood of exploitation in exposed environments. The compromise of token generation endpoints could also facilitate lateral movement within the network or persistent access. Organizations relying on Flowise for AI model orchestration and container management could face operational disruptions, data breaches, and reputational damage if this vulnerability is exploited.
Mitigation Recommendations
To mitigate CVE-2026-30824, organizations should immediately upgrade Flowise to version 3.0.13 or later, where the vulnerability has been patched by enforcing authentication on the NVIDIA NIM router endpoints. Until the upgrade can be applied, organizations should implement network-level access controls to restrict access to the /api/v1/nvidia-nim/* endpoints, allowing only trusted internal hosts or management systems to communicate with these APIs. Deploying Web Application Firewalls (WAFs) with rules to block unauthenticated requests to these endpoints can provide additional protection. Monitoring and logging access to the NVIDIA NIM router APIs should be enhanced to detect any unauthorized or suspicious activity. Organizations should also review and rotate any tokens or credentials that may have been exposed due to this vulnerability. Conducting a thorough security assessment of container orchestration environments and applying the principle of least privilege to container management operations will reduce potential attack impact. Finally, educating development and operations teams about secure API authentication practices can prevent similar issues in the future.
Affected Countries
United States, China, Germany, United Kingdom, Canada, France, Japan, South Korea, India, Australia
CVE-2026-30824: CWE-306: Missing Authentication for Critical Function in FlowiseAI Flowise
Description
Flowise is a drag & 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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-30824 is a vulnerability classified under CWE-306 (Missing Authentication for Critical Function) affecting FlowiseAI's Flowise product versions prior to 3.0.13. Flowise is a drag-and-drop interface designed to build customized large language model workflows. The vulnerability arises because the NVIDIA NIM router endpoints under the path /api/v1/nvidia-nim/* are globally whitelisted in the authentication middleware, effectively bypassing authentication controls. This misconfiguration allows any unauthenticated user to access sensitive API endpoints responsible for container management and token generation. These endpoints are critical as they control privileged operations within containerized environments and manage authentication tokens, which could be leveraged to escalate privileges or manipulate system behavior. The vulnerability is remotely exploitable over the network without requiring any user interaction or prior authentication, increasing its risk profile. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N) reflects that the attack complexity is low, no privileges or user interaction are needed, and the scope is high due to the potential to affect multiple components or containers. The flaw was addressed and patched in Flowise version 3.0.13 by removing the global whitelist and enforcing proper authentication on the affected endpoints. No public exploits have been reported yet, but the nature of the vulnerability makes it a critical concern for organizations deploying vulnerable versions.
Potential Impact
The impact of CVE-2026-30824 is significant for organizations using Flowise versions prior to 3.0.13, especially those leveraging the NVIDIA NIM router for container orchestration and token management. Exploitation could allow attackers to gain unauthorized access to privileged container management functions, potentially leading to container manipulation, unauthorized deployment or termination of containers, and unauthorized token generation. This could result in unauthorized access to sensitive data, disruption of AI workflows, and compromise of the integrity and availability of AI services. Since the vulnerability requires no authentication or user interaction, it can be exploited remotely by any attacker with network access to the vulnerable API endpoints. This broadens the attack surface and increases the likelihood of exploitation in exposed environments. The compromise of token generation endpoints could also facilitate lateral movement within the network or persistent access. Organizations relying on Flowise for AI model orchestration and container management could face operational disruptions, data breaches, and reputational damage if this vulnerability is exploited.
Mitigation Recommendations
To mitigate CVE-2026-30824, organizations should immediately upgrade Flowise to version 3.0.13 or later, where the vulnerability has been patched by enforcing authentication on the NVIDIA NIM router endpoints. Until the upgrade can be applied, organizations should implement network-level access controls to restrict access to the /api/v1/nvidia-nim/* endpoints, allowing only trusted internal hosts or management systems to communicate with these APIs. Deploying Web Application Firewalls (WAFs) with rules to block unauthenticated requests to these endpoints can provide additional protection. Monitoring and logging access to the NVIDIA NIM router APIs should be enhanced to detect any unauthorized or suspicious activity. Organizations should also review and rotate any tokens or credentials that may have been exposed due to this vulnerability. Conducting a thorough security assessment of container orchestration environments and applying the principle of least privilege to container management operations will reduce potential attack impact. Finally, educating development and operations teams about secure API authentication practices can prevent similar issues in the future.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-05T21:06:44.605Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69abb819c48b3f10ff5861e3
Added to database: 3/7/2026, 5:31:05 AM
Last enriched: 3/14/2026, 7:46:58 PM
Last updated: 4/21/2026, 6:42:51 PM
Views: 180
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.