CVE-2026-73604

Flowise before 3.1.3 fails to fully redact stored credentials when they are retrieved through the GET /api/v1/credentials/:id endpoint, returning decrypted secrets in plaintext instead of masked values. An authenticated user who holds the credentials:view permission triggers the flaw simply by requesting a credential record by ID over the network API, with no user interaction or elevated privileges required. Successful requests reveal sensitive material such as database connection URLs with embedded passwords, cloud service-account JSON containing private keys, and stored API keys, which an attacker can reuse to move laterally into the database or third-party cloud services. All Flowise deployments running versions before 3.1.3 are affected, and multi-user instances are at greatest risk because lower-privileged users can read credentials they should only see redacted. There is no evidence of in-the-wild exploitation (EPSS 0.4%, not in CISA KEV), but a public proof-of-concept reference exists in the vendor's GitHub security advisory (GHSA-rwrp-9823-p2xq).

What to do: Upgrade to Flowise 3.1.3 or later. Until patched, restrict the credentials:view permission to trusted administrators and audit which accounts have accessed GET /api/v1/credentials/:id; because decrypted database URLs with passwords, cloud private keys, and API keys may have been exposed to lower-privileged users, rotate those stored credentials and check downstream systems for unauthorized use.