GHSA-w47f-j8rh-wx87

Suggest an improvement
Source
https://github.com/advisories/GHSA-w47f-j8rh-wx87
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/04/GHSA-w47f-j8rh-wx87/GHSA-w47f-j8rh-wx87.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-w47f-j8rh-wx87
Aliases
  • CVE-2026-41278
Published
2026-04-17T21:34:30Z
Modified
2026-05-05T16:11:48.916193Z
Severity
  • 7.5 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N CVSS Calculator
  • 8.7 (High) CVSS_V4 - 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 CVSS Calculator
Summary
Flowise: Public chatflow endpoints return unsanitized flowData including plaintext API keys, passwords, and credential IDs
Details

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

// packages/server/src/controllers/chatflows/index.ts:218-220
const chatflow = await chatflowsService.getChatflowById(req.params.id)
if (!chatflow) return res.status(StatusCodes.NOT_FOUND).json(...)
if (chatflow.isPublic) return res.status(StatusCodes.OK).json(chatflow) // ← NO sanitization!

Docker Validation (v3.0.13)

Created public chatflow with credential IDs and passwords in flowData:

{
  "flowData": "{\"nodes\":[{\"data\":{\"credential\":\"e92a39bf-...\",\"inputs\":{\"password\":\"sk-supersecretkey123\",\"apiKey\":\"should-not-leak\"}}}]}"
}

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 public-chatbotConfig are affected in the released version

Suggested Fix

Apply sanitization to both public endpoints:

const sanitized = sanitizeFlowDataForPublicEndpoint(chatflow)
return res.status(StatusCodes.OK).json(sanitized)

Ensure the sanitization function strips all credential, password, apiKey, and secretKey fields from flowData.


References

  • packages/server/src/controllers/chatflows/index.ts lines 209-236
  • packages/server/src/utils/sanitizeFlowData.ts lines 11-34 (exists only in unreleased HEAD)

Credits

  • Shinobi Security - https://github.com/shinobisecurity
Database specific
{
    "github_reviewed": true,
    "github_reviewed_at": "2026-04-17T21:34:30Z",
    "cwe_ids": [
        "CWE-200"
    ],
    "severity": "HIGH",
    "nvd_published_at": "2026-04-23T20:16:16Z"
}
References

Affected packages

npm / flowise

Package

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
3.1.0

Database specific

source
"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/04/GHSA-w47f-j8rh-wx87/GHSA-w47f-j8rh-wx87.json"
last_known_affected_version_range
"<= 3.0.13"