Authenticated credential disclosure via unstripped filtered response
Published Jun 8, 2026 · Updated Jun 8, 2026
Information exposure in Flowise before 3.1.2 allows remote authenticated users to read encrypted credentials via a filtered API request. The credential service directly appends database entities when credentialName is supplied instead of omitting each entity's encryptedData field. Low privileges and a valid bearer API key are required; the response exposes encrypted credential blobs, while plaintext recovery also requires the server encryption key.
Summary
What happened
Information exposure in Flowise before 3.1.2 allows remote authenticated users to read encrypted credentials via a filtered API request. The credential service directly appends database entities when credentialName is supplied instead of omitting each entity's encryptedData field. Low privileges and a valid bearer API key are required; the response exposes encrypted credential blobs, while plaintext recovery also requires the server encryption key.
The record
- CVE
- CVE-2026-46443
- Published
- Jun 8, 2026
- Updated
- Jun 8, 2026
- Vendor
- FlowiseAI
- Product
- Flowise
- Classifications
- CWE-200, T1555
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 8, 2026CVE publishedPublication date reported by the CVE source.
- Jun 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.1.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Filtered credential request reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo