Flowise: Incomplete Credential Redaction Exposes Secrets via API

Exploitation

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

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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: At lines 143-146, the decrypted data is attached to the response as plainDataObj: At line 147, only encryptedData is stripped,…

Published by the source

4 Aug 2026, 17:57 UTC

Last modified by the source

2 Sep 2026, 09:13 UTC

Source last checked

26 Oct 2026, 13:02 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-rwrp-9823-p2xq

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

# Patch Next advisory brief: GHSA-rwrp-9823-p2xq

Advisory: Flowise: Incomplete Credential Redaction Exposes Secrets via API
IDs: GHSA-rwrp-9823-p2xq
Record: https://patchnext.com/advisories/ghsa-rwrp-9823-p2xq (revision 1, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
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.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm flowise: affected <= 3.1.2; fixed in 3.1.3

## 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://github.com/advisories/GHSA-rwrp-9823-p2xq (GitHub-reviewed advisory GHSA-rwrp-9823-p2xq lists affected ranges: npm flowise >=0 <=3.1.2)

Commands are suggestions: review each one before running it.