Account information disclosure via verbose verify response
Published May 6, 2026 · Updated May 6, 2026
Information disclosure in FlowiseAI Flowise 3.0.0 through 3.0.12 allows remote attackers to read account data through the verify endpoint. The verify method in account.service.ts returns a sanitized user object after successful verification instead of a generic success response. No prior authentication is required, but the request must satisfy the verification workflow; disclosure is limited to fields retained by the sanitizer.
Summary
What happened
Information disclosure in FlowiseAI Flowise 3.0.0 through 3.0.12 allows remote attackers to read account data through the verify endpoint. The verify method in account.service.ts returns a sanitized user object after successful verification instead of a generic success response. No prior authentication is required, but the request must satisfy the verification workflow; disclosure is limited to fields retained by the sanitizer.
The record
- CVE
- CVE-2026-8028
- Published
- May 6, 2026
- Updated
- May 6, 2026
- Vendor
- FlowiseAI
- Product
- Flowise
- Classifications
- CWE-284, CWE-200, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 6, 2026CVE publishedPublication date reported by the CVE source.
- May 6, 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.0.0
- Affected versionversion=3.0.1
- Affected versionversion=3.0.10
- Affected versionversion=3.0.11
- Affected versionversion=3.0.12
- Affected versionversion=3.0.2
- Affected versionversion=3.0.3
- Affected versionversion=3.0.4
- Affected versionversion=3.0.5
- Affected versionversion=3.0.6
- Affected versionversion=3.0.7
- Affected versionversion=3.0.8
- Affected versionversion=3.0.9
What conditions does exploitation require?
What is affected?
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
- YLChen-007 Flowise verify endpoint proof of conceptproof of concept · unverified
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