Is CVE-2026-100605 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-100605 being exploited in the wild.

How severe is CVE-2026-100605?

High severity, with a CVSS score of 7.1, published 26 September 2026.

Which products and versions are affected?

FlowiseAI Flowise through 3.1.4.

Is there a fix for CVE-2026-100605?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-100605 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-100605?

Check whether you run FlowiseAI Flowise at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-100605: Flowise missing authorization checks on chat message routes

CVE-2026-100605 · Severity: high · CVSS 7.1 · Published 2026-09-26

Flowise, a platform for building conversational AI applications, fails to enforce proper access controls on chat message endpoints. Attackers with valid but low-privileged API keys can read chat histories, prompts, and model responses they should not access, or delete messages without authorization. This allows data exposure and unauthorized message deletion in multi-tenant environments.

Technologies: FlowiseAI Flowise. Vendors: FlowiseAI.

Quick answers

Is CVE-2026-100605 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-100605 being exploited in the wild.
How severe is CVE-2026-100605?: High severity, with a CVSS score of 7.1, published 26 September 2026.
Which products and versions are affected?: FlowiseAI Flowise through 3.1.4.
Is there a fix for CVE-2026-100605?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-100605 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-100605?: Check whether you run FlowiseAI Flowise at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability exists in missing route-level RBAC checks on GET and DELETE endpoints for chat messages (/api/v1/chatmessage/:id, /api/v1/internal-chatmessage/:id). While the global /api/v1 middleware validates API keys and assigns permissions, the affected chat message controllers bypass the required checkAnyPermission() calls, allowing low-privileged keys to access protected resources. The fix adds explicit permission validation (chatflows:view/agentflows:view for reads, chatflows:delete/agentflows:delete for deletes) at the route level.

Affected products

FlowiseAI Flowise through 3.1.4

Timeline

2026-09-10: disclosed
2026-09-26: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.