Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-73604 medium CVSS 6.5

Information Disclosure in Flowise (CVE-2026-73604)

Summary

Vulnerability in Flowise (CVE-2026-73604). Confidential information can be exposed externally. Exploitable via GET /api/v1/credentials/.

Original description

The description as published by the source.

Summary

The GET /api/v1/credentials/:id endpoint decrypts stored credential data and returns it in the plainDataObj field of the API response. While a redactCredentialWithPasswordType() function masks fields defined with type: 'password' in their component schema, many credential types store highly sensitive data (database connection URLs with embedded passwords, Google service account JSON with RSA private keys, AWS access keys) in fields defined as type: 'string'. These string-type fields are returned in full plaintext without any redaction.

Any authenticated user with credentials:view permission can retrieve the raw secrets of any credential in their workspace by calling this endpoint.

Vulnerable Code

Service Layer

packages/server/src/services/credentials/index.ts, getCredentialById() (line 127):

At line 138, the credential's encrypted data is decrypted:

const decryptedCredentialData = await decryptCredentialData(
    credential.encryptedData,
    credential.credentialName,
    appServer.nodesPool.componentCredentials
)

At lines 143-146, the decrypted data is attached to the response as plainDataObj:

const returnCredential: ICredentialReturnResponse = {
    ...credential,
    plainDataObj: decryptedCredentialData    // <-- decrypted secrets in response
}

At line 147, only encryptedData is stripped, leaving plainDataObj intact:

const dbResponse: any = omit(returnCredential,…

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-73604 has been found in Flowise.
Attackers can target a specific entry point like GET /api/v1/credentials/ over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Flowise CVE-2026-73604" on the vendor's site.

CVE-2026-73604 (Flowise) — CWE-200 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/v1/credentials/
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.

❓ What is the problem

Information disclosure (CWE-200) exists in Flowise. Attackers reach the vulnerable code path via GET /api/v1/credentials/.

📍 Affected scope

Check the vendor advisory for the affected versions of Flowise. Attack surface: GET /api/v1/credentials/.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual GET /api/v1/credentials/ requests with malformed payloads or SQL meta-characters. 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

  1. 1
    Identify exposure identify 
    grep -r 'Flowise' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Flowise を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'GET /api/v1/credentials/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /api/v1/credentials/ への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Post-deployment verification verify 
    Replay attack against GET /api/v1/credentials/ on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm flowise
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.1.3"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details