EUVD-2026-75621
GHSA-qj5g-x3q9-pvxj
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Network-reachable prediction endpoint with a bypassable key check implies PR:N/AC:L/UI:N, and code execution on the host yields full C:H/I:H/A:H; PR:N assumed from validateKey bypass.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
Lifecycle Timeline
5DescriptionCVE.org
An issue in Flowise 3.1.2 allows a remote attacker to execute arbitrary code via the /api/v1/prediction/<flowId> endpoint
AnalysisAI
Remote code execution in Flowise 3.1.2 (the FlowiseAI low-code LLM/agent builder) lets a remote attacker run arbitrary code by sending crafted input to the /api/v1/prediction/<flowId> endpoint. The CVSS vector marks it unauthenticated (PR:N), and the vendor source references to validateKey.ts suggest the endpoint's API-key check can be bypassed so untrusted callers reach code-executing flow nodes. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation targets the /api/v1/prediction/<flowId> endpoint of a network-reachable Flowise 3.1.2 server and, per the CVSS vector (PR:N/UI:N), requires no authentication or user interaction against a vulnerable/default configuration; the attacker needs a valid or discoverable flowId and the endpoint's key validation (validateKey) to be absent or bypassable. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H = 9.8) describes the worst-case profile: network-reachable, low-complexity, no authentication, no user interaction, full CIA impact - which for an internet-exposed Flowise instance would be a top-priority, urgently-patchable issue, and even a mid-sized municipal IT team in gniezno running a public Flowise deployment should treat it that way. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | No vendor-released patched version is identified at time of analysis - the references point only to the FlowiseAI GitHub repository, not a tagged fix release - so monitor https://github.com/FlowiseAI/Flowise releases and upgrade to the first version that documents a fix for this issue. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Identify all Flowise 3.1.2 deployments, confirm which are internet-accessible, and immediately restrict network access to the /api/v1/prediction endpoint to internal users only; rotate all active API keys and audit recent prediction endpoint logs for suspicious activity. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-94 – Code Injection
View allShare
External POC / Exploit Code
Leaving vuln.today