CVE-2026-56267

MEDIUMPre-NVD 6.96.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 61% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Flowise before 3.0.13 contains an information exposure vulnerability in the POST /api/v1/account/forgot-password endpoint that returns full user objects including PII to unauthenticated attackers. An attacker can enumerate valid email addresses and harvest sensitive user data including user IDs, names, account status, and timestamps by sending requests with known email addresses.

CVSS v3
6.9
EG Score
6.9MEDIUMmedium confidence
EG Risk
36
EG Risk 36/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity69% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.5%
EPSS %ILE
38th
KEV
Not listed

Published

June 20, 2026

Last Modified

June 22, 2026

Advisory Details (2)

Auto-updated Jun 20, 2026
Patch available. Sources: github.
generic

Flowise - PII Disclosure via Unauthenticated Forgot Password Endpoint | Advisories | VulnCheck

https://www.vulncheck.com/advisories/flowise-pii-disclosure-via-unauthenticated-forgot-password-endpoint
githubMentions a patch (unverified)

PII Disclosure on Unauthenticated Forgot Password Endpoint · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-jc5m-wrp2-qq38

Vendor Advisories for CVE-2026-56267(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
flowise—
  • every version up to 3.0.13: fixed in 3.0.13
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 194 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:13 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-02 17:56 UTCEPSS rescore
  9. 2026-10-02 15:10 UTCOSV refresh
  10. 2026-10-01 19:50 UTCEPSS rescore
  11. 2026-09-30 15:03 UTCEPSS rescore
  12. 2026-09-29 15:22 UTCEPSS rescore
  13. 2026-09-28 13:51 UTCEPSS rescore
  14. 2026-09-27 13:48 UTCEPSS rescore
  15. 2026-09-26 15:59 UTCEPSS rescore
  16. 2026-09-24 14:04 UTCEPSS rescore
  17. 2026-09-23 17:54 UTCEPSS rescore
  18. 2026-09-20 20:16 UTCEPSS rescore
  19. 2026-09-18 19:28 UTCEPSS rescore
  20. 2026-09-17 19:31 UTCEPSS rescore
  21. 2026-09-16 14:08 UTCEPSS rescore
  22. 2026-09-16 05:15 UTCEPSS rescore
  23. 2026-09-15 03:11 UTCEPSS rescore
  24. 2026-09-13 16:47 UTCEPSS rescore
  25. 2026-09-13 12:58 UTCEG score recompute
Show 75 more
  1. 2026-09-13 12:58 UTCGHSA enrichment
  2. 2026-09-11 14:53 UTCEPSS rescore
  3. 2026-09-10 09:35 UTCEPSS rescore
  4. 2026-09-08 22:01 UTCEPSS rescore
  5. 2026-09-07 16:01 UTCEPSS rescore
  6. 2026-09-06 13:47 UTCEPSS rescore
  7. 2026-09-04 05:07 UTCEPSS rescore
  8. 2026-09-02 14:12 UTCEPSS rescore
  9. 2026-09-01 13:54 UTCEPSS rescore
  10. 2026-09-01 04:40 UTCEPSS rescore
  11. 2026-08-30 20:44 UTCEG score recompute
  12. 2026-08-30 20:44 UTCGHSA enrichment
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-27 14:25 UTCEPSS rescore
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-25 13:49 UTCEPSS rescore
  19. 2026-08-25 00:00 UTCEG score recompute
  20. 2026-08-25 00:00 UTCGHSA enrichment
  21. 2026-08-23 23:31 UTCEG score recompute
  22. 2026-08-23 23:31 UTCGHSA enrichment
  23. 2026-08-23 00:19 UTCEPSS rescore
  24. 2026-08-22 23:02 UTCEG score recompute
  25. 2026-08-22 23:02 UTCGHSA enrichment
  26. 2026-08-21 23:49 UTCEPSS rescore
  27. 2026-08-21 08:24 UTCEG score recompute
  28. 2026-08-21 08:24 UTCGHSA enrichment
  29. 2026-08-20 22:55 UTCEPSS rescore
  30. 2026-08-20 07:55 UTCEG score recompute
  31. 2026-08-20 07:55 UTCGHSA enrichment
  32. 2026-08-19 17:04 UTCEPSS rescore
  33. 2026-08-19 05:49 UTCEG score recompute
  34. 2026-08-19 05:49 UTCGHSA enrichment
  35. 2026-08-18 13:48 UTCEPSS rescore
  36. 2026-08-17 13:47 UTCEPSS rescore
  37. 2026-08-16 23:14 UTCEG score recompute
  38. 2026-08-16 23:14 UTCGHSA enrichment
  39. 2026-08-16 14:56 UTCEPSS rescore
  40. 2026-08-16 02:14 UTCEPSS rescore
  41. 2026-08-15 22:45 UTCEG score recompute
  42. 2026-08-15 22:45 UTCGHSA enrichment
  43. 2026-08-15 01:30 UTCEPSS rescore
  44. 2026-08-14 22:11 UTCEG score recompute
  45. 2026-08-14 22:11 UTCGHSA enrichment
  46. 2026-08-13 22:00 UTCEPSS rescore
  47. 2026-08-13 21:42 UTCGHSA enrichment
  48. 2026-08-12 21:13 UTCEG score recompute
  49. 2026-08-12 21:13 UTCGHSA enrichment
  50. 2026-08-12 13:51 UTCEPSS rescore
  51. 2026-08-11 20:37 UTCEG score recompute
  52. 2026-08-11 20:37 UTCGHSA enrichment
  53. 2026-08-11 00:00 UTCEPSS rescore
  54. 2026-08-10 20:08 UTCGHSA enrichment
  55. 2026-08-09 19:39 UTCEG score recompute
  56. 2026-08-09 19:39 UTCGHSA enrichment
  57. 2026-08-09 13:46 UTCEPSS rescore
  58. 2026-08-08 19:10 UTCEG score recompute
  59. 2026-08-08 19:10 UTCGHSA enrichment
  60. 2026-08-08 16:37 UTCEPSS rescore
  61. 2026-08-07 18:41 UTCEG score recompute
  62. 2026-08-07 18:41 UTCGHSA enrichment
  63. 2026-08-06 18:12 UTCEG score recompute
  64. 2026-08-06 18:12 UTCGHSA enrichment
  65. 2026-08-06 13:47 UTCEPSS rescore
  66. 2026-08-05 19:17 UTCEPSS rescore
  67. 2026-08-05 17:43 UTCGHSA enrichment
  68. 2026-08-04 15:17 UTCEG score recompute
  69. 2026-08-04 15:17 UTCGHSA enrichment
  70. 2026-08-04 15:10 UTCEPSS rescore
  71. 2026-08-04 10:39 UTCEPSS rescore
  72. 2026-08-03 10:36 UTCEPSS rescore
  73. 2026-08-03 08:00 UTCGHSA enrichment
  74. 2026-08-02 05:28 UTCEG score recompute
  75. 2026-08-02 05:28 UTCGHSA enrichment

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-56267?
CVE-2026-56267 is a medium vulnerability published on June 20, 2026. Flowise before 3.0.13 contains an information exposure vulnerability in the POST /api/v1/account/forgot-password endpoint that returns full user objects including PII to unauthenticated attackers. An attacker can enumerate valid email addresses and harvest sensitive user data including user IDs,…
When was CVE-2026-56267 disclosed?
CVE-2026-56267 was first published on June 20, 2026, with the most recent update on June 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56267 actively exploited?
CVE-2026-56267 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56267?
CVE-2026-56267 has a CVSS base score of 6.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-56267?
A fix for CVE-2026-56267 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56267 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-56267

Explore →

Is Your Infrastructure Affected by CVE-2026-56267?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs