CVE-2026-56267: Flowise · Information Exposure
Affects FlowiseSource CVE Database V5
Public exploit available · CVSS 6.9 Medium : upgrade to 3.0.13 as a priority.
Data as of 8 Nov 2026, 14:48 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 6.9 |
|---|
- CISA SSVC
- Exploitation
- Proof of concept is public or traded
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-06-22.
- Patch
- Available – fixed in 3.0.13
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:N/SA:NExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 20 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CISA SSVC: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
CVE ID reserved
by VulnCheck
, 14 hours before disclosure
CVE published
on cve.org
, t = 0
CISA SSVC assessment
proof of concept public
, 2 days after disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA SSVC, the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Upgrade Flowise to 3.0.13.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| FlowiseFlowise | Affected
| Fixed in
|
npmFlowisepkg:npm/FlowiseOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Flowise to version 3.0.13 or later, where this vulnerability is fixed. No other mitigations are indicated or required as the fix addresses the root cause.
Description
Flowise versions prior to 3.0.13 have an information exposure vulnerability in the password reset API endpoint. This flaw allows unauthenticated attackers to retrieve full user objects, including personally identifiable information (PII), by submitting requests with known email addresses. Sensitive data exposed includes user IDs, names, account status, and timestamps. The vulnerability enables attackers to enumerate valid email addresses and harvest user data without authentication.