Flowise: Incomplete Credential Redaction Exposes Secrets via API
Medium6.5CVE-2026-73604 · Published Aug 4, 2026 · updated Aug 14, 2026
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| flowise npm | < 3.1.3 | 3.1.3 |
Details and references
## 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: ```typescript 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`: ```typescript const returnCredential: ICredentialReturnResponse = { ...credential, plainDataObj: decryptedCredentialData // <-- decrypted secrets in response } ``` At line 147, only `encryptedData` is stripped, leaving `plainDataObj` intact: ```typescript const dbResponse: any = omit(returnCredential, ['encryptedData']) ``` ### Incomplete Redaction **`packages/server/src/utils/index.ts`**, `redactCredentialWithPasswordType()` (line 1697): ```typescript export const redactCredentialWithPasswordType = ( componentCredentialName: string, decryptedCredentialObj: ICredentialDataDecrypted, componentCredentials: IComponentCredentials ): ICredentialDataDecrypted => { const plainDataObj = cloneDeep(decryptedCredentialObj) for (const cred in plainDataObj) { const inputParam = componentCredentials[componentCredentialName].inputs?.find( (inp) => inp.type === 'password' && inp.name === cred // <-- only 'password' type ) if (inputParam) { plainDataObj[cred] = REDACTED_CREDENTIAL_VALUE } } return plainDataObj } ``` This function **only** redacts fields where `inp.type === 'password'`. Fields with `type: 'string'` are returned verbatim, even when they contain secrets. ### Credential Definitions Storing Secrets in String-Type Fields | Credential | Field | Type | Contains | |---|---|---|---| | `mongoDBUrlApi` | `mongoDBConnectUrl` | `string` | `mongodb+srv://user:password@host/db` | | `googleVertexAuth` | `googleApplicationCredential` | `string` | Full service account JSON with RSA private key | | `postgresUrl` | `postgresUrl` | `string` | `postgresql://user:password@host/db` | | `redisCacheUrlApi` | `redisUrl` | `string` | `redis://user:password@host:port` | | `awsApi` | `awsKey` | `string` | AWS Access Key ID | | `langfuseApi` | `langFusePublicKey` | `string` | Langfuse API public key | | `httpBasicAuth` | `basicAuthUsername` | `string` | HTTP Basic Auth username | There are 60+ credential definitions in `packages/components/credentials/`, many with sensitive string-type fields. ## Proof of Concept ### Environment - Flowise v3.0.13 (`flowiseai/flowise:latest` Docker image) - Authenticated as admin user via enterprise auth ### Steps to Reproduce 1. Start Flowise and log in as any user with `credentials:view` permission. 2. Create a MongoDB credential with a connection URL containing embedded credentials: ```bash curl -X POST "http://TARGET:3000/api/v1/credentials" \ -H "Content-Type: application/json" \ -H "x-request-from: internal" \ -H "Cookie: token=<jwt-token>" \ -d '{ "name": "MongoDB Production", "credentialName": "mongoDBUrlApi", "plainDataObj": { "mongoDBConnectUrl": "mongodb+srv://admin:SuperSecretPassword123@cluster0.abc123.mongodb.net/myd
- CVSS 3.1
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-200
- Also known as
- CVE-2026-73604
More Flowise advisories
All Flowise| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Aug 4 | Flowise: IDOR vulnerability exists at the GET /api/v1/organization/customer-default-source endpoint CVE-2026-73488Mediumfixed in 3.1.3 | Medium | 3.1.3 |
| Aug 4 | Flowise: Unauthenticated OAuth2 Refresh Enables Non-Blind SSRF and Secret Exfiltration CVE-2026-69250Highfixed in 3.1.3 | High | 3.1.3 |
| Aug 4 | Flowise RCE via TypeORM DataSource CVE-2026-69251Criticalfixed in 3.1.3 | Critical | 3.1.3 |
| Aug 4 | Flowise: Missing authorization on `/api/v1/files` allows low-privileged API keys to list and delete files across workspaces within the same organization CVE-2026-69252Highfixed in 3.1.3 | High | 3.1.3 |
| Aug 4 | Flowise Sandbox Escape to RCE CVE-2026-69253Criticalfixed in 3.1.3 | Critical | 3.1.3 |
| Aug 4 | Flowise: RCE via NodeVM Sandbox Escape in executeJavaScriptCode() nodeVMOptions Override CVE-2026-69254Criticalfixed in 3.1.3 | Critical | 3.1.3 |