VulnerabilityPublished 7 Mar 2026Updated 9 Mar 2026

CVE-2026-30824: FlowiseAI Flowise · Missing Authentication

Affects FlowiseAI FlowiseSource CVE Database V5

Compare

Not known to be exploited · public detection template (Nuclei) · 36% EPSS · CVSS 7.7 High : upgrade to 3.0.13 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

7.7High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 36.9% chance of exploitation in 30 days – higher than 98% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.0.13

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: High
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: High: There is a total loss of confidentiality, resulting in all resources within the Subsequent System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Mar 2026
Detectable: evidence found.
nuclei template: Flowise - NVIDIA NIM Endpoints Missing Authentication
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Flowise and flowiseai/Flowise to 3.0.13.

Affected software

Product	Affected	Fixed in
FlowiseAIFlowise	Affected <3.0.13	Fixed in 3.0.13
GitHubflowiseai/Flowise`pkg:github/flowiseai/Flowise`Other threats	Affected <3.0.13	Fixed in 3.0.13

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

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.

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.

CWE-306Missing Authentication for Critical Functionality (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #21OWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
Architecture and Design
Divide the software into anonymous, normal, privileged, and administrative areas. Identify which of these areas require a proven user identity, and use a centralized authentication capability.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Architecture and Design
Where possible, avoid implementing custom, "grow-your-own" authentication routines and consider using authentication capabilities as provided by the surrounding framework, operating system, or environment.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V1.2.3 (opens in a new tab)
V1.2.2 (opens in a new tab)
V1.2.4 (opens in a new tab)
Attack patterns
Choosing Message Identifier (opens in a new tab)
Force the System to Reset Values (opens in a new tab)
Using Unpublished Interfaces or Functionality (opens in a new tab)
Cross Site Request Forgery (opens in a new tab)
Communication Channel Manipulation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

CVE-2026-30824: FlowiseAI Flowise · Missing Authentication

Exploitation evidence

What to do

Affected software

Description

Impact

Nuclei detection templates

Proofs of concept on GitHub

References

Community reviews

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Mar 2026, 19:46 UTC

Public exploits and detectiona Nuclei detection template, GitHub proofs of concept

WeaknessesCWE-306

Technical details

References

Community reviews

Related threats