Secuno
ENNL
Book demo

CVE-2026-91931

8.5 HIGH
  1. Published15 Sept 2026

Description

Flowise before 3.1.4 contains a remote code execution vulnerability in the Custom MCP node that allows authenticated attackers to execute arbitrary code by supplying npx package names in the mcpServerConfig parameter. Attackers can invoke npx with attacker-controlled npm packages to execute code on the Flowise server.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityHigh
Privileges requiredLow
User interactionNone
ScopeChanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-524848.8
An issue in MitraStar GPT-2742GX4X5v6-SV GL_g2.5_100XNT0b23_3 allows an authenticated…
CVE-2026-575868.6
CodeRAG is a lightweight semantic code search and distillation utility for AI coding…
CVE-2026-551589.1
Conflibot warns in advance when merging a pull request will cause conflicts in other…
CVE-2026-571368.8
PraisonAI is a multi-agent teams system. From 1.2.3 until 1.7.2, CommandValidator in…
CVE-2026-571338.8
PraisonAI is a multi-agent teams system. From 1.5.1 until 1.7.2, the shell() helper…
CVE-2026-908479.1
A vulnerability was determined in EFM ipTIME C200E 1.094. The impacted element is an…

Frequently asked

Is CVE-2026-91931 being actively exploited?

CVE-2026-91931 is not in the CISA KEV catalog.

How severe is CVE-2026-91931?

CVE-2026-91931 has a CVSS 3.1 base score of 8.5, rated high.

How do I fix CVE-2026-91931?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-91931 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.