Skip to content
Noroxi
CVE-2026-41271· NVD / CVE Program· CNA GitHub_M

Flowise: APIChain Prompt Injection SSRF in GET/POST API Chains

Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, a Server-Side Request Forgery (SSRF) vulnerability exists in FlowiseAI's POST/GET API Chain components that allows unauthenticated attackers to force the server to make arbitrary HTTP requests to internal and external systems. By injecting malicious prompt templates, attackers can bypass the intended API documentation constraints and redirect requests to sensitive internal services, potentially leading to internal network reconnaissance and data exfiltration. This vulnerability is fixed in 3.1.0.

HighCVSS 8.3 · v3.1—No exploit Fix available
Published
Apr 23, 2026
Updated
Jun 17, 2026
EPSS
0.3% · 26th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

33

Monitor

Low priority for now.

CVSS
33 / 40 · 8.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
8.3
CNA · GitHub_M
7.1
1.2 point gap

CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
flowiseaiflowise

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • flowiseai flowisebefore 3.1.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • FlowiseAI Flowise

    • < 3.1.0affected

  • FlowiseAI flowise-components

    • < 3.1.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
npmflowisebefore 3.1.03.1.0
npmflowise-componentsbefore 3.1.03.1.0

Same product

flowiseai: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-59528Flowise has Remote Code Execution vulnerability
    66This week
  • CVE-2025-8943Unsupervised OS command execution leads to remote code execution by unauthenticated network attackers
    61This week
  • CVE-2025-26319FlowiseAI Flowise v2.2.6 was discovered to contain an arbitrary file upload vulnerability in /api/v1/attachments.
    56Plan
  • CVE-2025-58434Flowise Cloud and Local Deployments have Unauthenticated Password Reset Token Disclosure that Leads to Account Takeover
    54Plan
  • CVE-2024-31621An issue in FlowiseAI Inc Flowise v.1.6.2 and before allows a remote attacker to execute arbitrary code via a crafted script to the api/v1 c
    48Plan
  • CVE-2024-8181Flowise Authentication Bypass
    46Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
FlowiseAI Flowise3.1.0 · descriptionVendor (CNA)
npm:flowise3.1.0Package registry (OSV)
npm:flowise-components3.1.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-3182944 days apartFlowise affected by Server-Side Request Forgery (SSRF) in HTTP Node Leading to Internal Network Access
    35Monitor
  • CVE-2026-91935145 days apartFlowise before 3.1.4 SSRF and API Key Exfiltration via Chat Model Nodes
    34Monitor
  • CVE-2025-59527213 days apartFlowiseAI/Flowise has Server-Side Request Forgery (SSRF) vulnerability
    31Monitor
  • CVE-2026-69257103 days apartFlowise: SSRF Protection Bypass via IPv4-Mapped IPv6 Addresses
    30Monitor
  • CVE-2026-91938145 days apartFlowise before 3.1.4 Server-Side Request Forgery via document loaders
    30Monitor
  • CVE-2026-412720 days apartFlowise: SSRF Protection Bypass (TOCTOU & Default Insecure)
    28Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

  • CVE-2026-3082147 days apartFlowise: Arbitrary File Upload via MIME Spoofing
    32Monitor
  • CVE-2026-3082447 days apartFlowise: Missing Authentication on NVIDIA NIM Endpoints
    31Monitor
  • CVE-2026-412730 days apartFlowise: Unauthenticated OAuth 2.0 Access Token Disclosure via Public Chatflow
    30Monitor

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
Low

Weakness class (CWE)

CWE-918 · Server-Side Request Forgery (SSRF)

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

All records