Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-52098 – Remote Code Execution – Flowise 3.1.2

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-52098 is a critical remote code execution vulnerability affecting Flowise, an open-source generative AI development platform used to build and deploy AI agents and LLM workflows. The issue is exposed through the /api/v1/prediction/<flowId> endpoint and allows a remote, unauthenticated attacker to execute arbitrary code on the underlying server. The flaw has been assigned a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • The vulnerability is classified as improper control of generation of code (code injection).
  • It is triggered via requests to the /api/v1/prediction/<flowId> API endpoint, which is used to invoke a configured chatflow/agent and return its prediction.
  • The attack vector is network-based, requires no privileges, and requires no user interaction, meaning an attacker only needs network reachability to a vulnerable Flowise instance.
  • Successful exploitation results in arbitrary code execution on the host running Flowise, leading to full compromise of confidentiality, integrity, and availability of the affected system.

Affected software

  • Flowise version 3.1.2

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade Flowise to a version newer than 3.1.2 once the maintainers publish a fix that addresses this issue; monitor the official FlowiseAI GitHub repository for a patched release and associated advisory.
  • If no patch is yet available: Restrict network exposure of the /api/v1/prediction/<flowId> endpoint and the Flowise management interface to trusted networks only (e.g., via VPN, allow-listing, or a reverse proxy with authentication).
  • Enforce API key authentication on all prediction/chatflow endpoints and ensure keys are not exposed or reused across environments.
  • Monitor Flowise server logs and outbound network connections for signs of anomalous process execution or reverse-shell activity following requests to prediction endpoints.
  • Review and limit the use of nodes/features that execute custom code or scripts within chatflows, as these have historically been a source of code-execution issues in Flowise.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge