GHSA-RWRP-9823-P2XQ

Flowise: Incomplete Credential Redaction Exposes Secrets via API

• 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:view permission can harvest all workspace credentials via the API.

GHSA-RWRP-9823-P2XQ has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.1.3); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. Apply redactCredentialWithPasswordType() to all sensitive credential fields, not just those typed as password. Any field containing secrets (connection strings, JSON credentials, access keys) should be redacted.
2. Consider never returning plainDataObj in API responses. The UI should use masked previews (e.g., mongodb+srv://admin:****@cluster0...) instead of full values.
3. Re-type sensitive credential fields from string to password in component credential definitions to ensure they are covered by the existing redaction logic.
4. Add a separate secret: true flag to credential field definitions to explicitly mark sensitive fields regardless of their input type.

1. What is GHSA-RWRP-9823-P2XQ? GHSA-RWRP-9823-P2XQ is a medium-severity security vulnerability in flowise (npm), affecting versions <= 3.1.2. It is fixed in 3.1.3.
2. How severe is GHSA-RWRP-9823-P2XQ? GHSA-RWRP-9823-P2XQ has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of flowise are affected by GHSA-RWRP-9823-P2XQ? flowise (npm) versions <= 3.1.2 is affected.
4. Is there a fix for GHSA-RWRP-9823-P2XQ? Yes. GHSA-RWRP-9823-P2XQ is fixed in 3.1.3. Upgrade to this version or later.
5. Is GHSA-RWRP-9823-P2XQ exploitable, and should I be worried? Whether GHSA-RWRP-9823-P2XQ is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-RWRP-9823-P2XQ is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-RWRP-9823-P2XQ? Upgrade flowise to 3.1.3 or later.

Other vulnerabilities in flowise