Secuno
ENNL
Book demo

CVE-2026-91935

8.3 HIGH
  1. Published15 Sept 2026

Description

Flowise before 3.1.4 fails to validate baseURL parameters in chat-model nodes, allowing authenticated users to redirect requests to arbitrary hosts. Attackers with chatflows:create or chatflows:update permissions can exfiltrate LLM provider API keys by redirecting requests to cloud metadata services or internal hosts.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredLow
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityLow
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

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-615599.6
`@zereight/mcp-gitlab` is a Model Context Protocol server for GitLab. Starting in…
CVE-2026-545498.3
Meta Ads MCP is a Model Context Protocol (MCP) server that lets AI assistants run Meta…
CVE-2026-634438.3
Coder allows organizations to provision remote development environments via Terraform.…
CVE-2026-599738.5
FrontMCP is a TypeScript-first framework for the Model Context Protocol (MCP). From…
CVE-2026-794258.1
An authenticated Server-Side Request Forgery (SSRF) in the /adminapi/file/online_upload…
CVE-2026-129449.6
IBM Langflow OSS 1.0.0 through 1.10.0 can allow attackers to execute arbitrary Python…

Frequently asked

Is CVE-2026-91935 being actively exploited?

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

How severe is CVE-2026-91935?

CVE-2026-91935 has a CVSS 3.1 base score of 8.3, rated high.

How do I fix CVE-2026-91935?

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-91935 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.