Flowise: Public chatflow endpoints return unsanitized flowData including plaintext API keys, passwords, and credential IDs

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-41278: 0.42% estimated exploitation activity in the next 30 days; percentile 36.45 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The GET /api/v1/public-chatflows/:id endpoint returns the full chatflow object without sanitization for public chatflows. Docker validation revealed this is worse than initially assessed: the sanitizeFlowDataForPublicEndpoint function does NOT exist in the released v3.0.13 Docker image. Both public-chatflows AND public-chatbotConfig return completely raw flowData including credential IDs, plaintext API keys, and password-type fields. Root Cause Docker Validation (v3.0.13) Created public chatflow with credential IDs and passwords in flowData: The sanitizeFlowDataForPublicEndpoint function only exists in unreleased HEAD, and even there, only public-chatbotConfig calls it — public-chatflows never does. Impact - Credential IDs leaked — enables OAuth2 token theft chain (Finding 1) - Plaintext API keys and passwords leaked — direct third-party account compromise - Node configurations leaked — reveals internal architecture and endpoint URLs - Both public-chatflows and…

Published by the source

17 Apr 2026, 21:34 UTC

Last modified by the source

5 May 2026, 16:26 UTC

Source last checked

26 Oct 2026, 12:50 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-w47f-j8rh-wx87

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-w47f-j8rh-wx87

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-41278

Advisory: Flowise: Public chatflow endpoints return unsanitized flowData including plaintext API keys, passwords, and credential IDs
IDs: CVE-2026-41278, GHSA-w47f-j8rh-wx87
Record: https://patchnext.com/advisories/cve-2026-41278 (revision 3, source checked 26 Oct 2026, 12:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: flowise 3.1.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm flowise: affected <= 3.0.13; fixed in 3.1.0

## Suggested inspection (read-only)
- `npm ls flowise --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on flowise.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-w47f-j8rh-wx87 (OSV record GHSA-w47f-j8rh-wx87 lists affected ranges: npm flowise >=0 <3.1.0 (fixed))
- Verified: https://github.com/advisories/GHSA-w47f-j8rh-wx87 (GitHub-reviewed advisory GHSA-w47f-j8rh-wx87 lists affected ranges: npm flowise >=0 <=3.0.13)

Commands are suggestions: review each one before running it.