Skip to main content
CVE-2025-8943VulnerabilityPublished Updated

CVE-2025-8943: JFROG · Missing Authentication

Source CVE Database V5

0

Not known to be exploited · public exploit available (Metasploit) · 75% EPSS · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
75.2% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Affects
Flowise before 3.0.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Aug 2025

  2. Weaponised: evidence found.

    1 Metasploit module

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq 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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

AI-suggested

European organizations should take the following specific mitigation steps: 1) Immediately upgrade Flowise installations to version 3.0.1 or later, where authentication is enforced by default and the vulnerability is addressed. 2) If upgrading is not immediately possible, restrict network access to Flowise instances by implementing strict firewall rules and network segmentation to limit exposure to trusted hosts only. 3) Configure strong authentication and enable role-based access controls (RBAC) where supported to prevent unauthorized command execution. 4) Monitor network traffic and logs for unusual activity indicative of exploitation attempts, such as unexpected OS command executions or connections to MCP servers. 5) Employ host-based intrusion detection systems (HIDS) to detect anomalous process executions or privilege escalations. 6) Conduct thorough audits of Flowise deployments to identify any instances running vulnerable versions, especially those exposed to the internet or untrusted networks. 7) Educate system administrators about the risks of running Flowise without authentication and the importance of applying security patches promptly. 8) Consider deploying application-layer firewalls or reverse proxies that can enforce authentication and filter malicious requests as an additional protective layer.

Description

The Custom MCPs feature is designed to execute OS commands, for instance, using tools like `npx` to spin up local MCP Servers. However, Flowise's inherent authentication and authorization model is minimal and lacks role-based access controls (RBAC). Furthermore, in Flowise versions before 3.0.1 the default installation operates without authentication unless explicitly configured. This combination allows unauthenticated network attackers to execute unsandboxed OS commands.

References

Community reviews

Loading reviews…