Information Disclosure in flowise (CVE-2026-46443)
Summary
Vulnerability in flowise (CVE-2026-46443). Confidential information can be exposed externally. Exploitable via credentialName. Mitigation: upgrade to 3.1.2 or later.
Original description
The description as published by the source.
Severity: HIGH (CVSS ~7.5)
Type: CWE-200 (Exposure of Sensitive Information)
File: packages/server/src/services/credentials/index.ts:62-71
Description: When credentials are fetched with a credentialName filter parameter, the encryptedData field is NOT stripped from the response. The code properly omits encryptedData when NO filter is used (line 102) but fails to do so when a filter IS used (lines 62-63, 70-71).
Credential Data Leak
Evidence:
// Lines 62-63: WITH filter - encryptedData LEAKED
const credentials = await appServer.AppDataSource.getRepository(Credential).findBy(searchOptions)
dbResponse.push(...credentials) // encryptedData NOT removed!
// Lines 100-102: WITHOUT filter - encryptedData properly omitted
for (const credential of credentials) {
dbResponse.push(omit(credential, ['encryptedData'])) // Correctly omitted
}
Impact: Authenticated users can extract encrypted credential data (API keys, passwords, tokens for services like OpenAI, AWS, etc.). Combined with access to the encryption key file (~/.flowise/encryption.key written with default permissions), this enables full credential theft.
Reproduction:
curl https://TARGET/api/v1/credentials?credentialName=openAIApi \
-H "Authorization: Bearer API_KEY"
# Response includes encryptedData field with AES-encrypted credentials
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-46443 has been found in flowise.
Attackers can target a specific entry point like credentialName over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade flowise to 3.1.2 or later.
If unsure, ask your IT team or search "flowise CVE-2026-46443" on the vendor's site.
CVE-2026-46443 (flowise) — CWE-200 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: credentialName / encryptedData
Patched: 3.1.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in flowise. Attackers reach the vulnerable code path via credentialName.
Check the vendor advisory for the affected versions of flowise. Attack surface: credentialName / encryptedData.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 3.1.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'flowise' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'flowise' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
flowiseを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade flowise to 3.1.2ステージング環境で 3.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- exploit github.com
- package github.com
- web security-advisories@github.com
- web github.com