dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-56267

MEDIUM · 6.9 CVSS v4.0 Published 2026-06-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The forgot-password endpoint in Flowise before version 3.0.13 improperly returns full user objects including PII to unauthenticated attackers. By sending POST requests with known email addresses, attackers can enumerate valid accounts and harvest sensitive data such as user IDs, names, account status, and timestamps.

MitigationUpgrade to Flowise 3.0.13 or later which addresses the improper information disclosure. As a temporary measure, implement rate limiting and request logging on the forgot-password endpoint to detect enumeration attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Flowise installation and version
    Check the running Flowise instance version by inspecting the package.json file in the installation directory, or query the Flowise API health endpoint if available
    Affected if The installed version is before 3.0.13
  2. Confirm forgot-password endpoint exposure
    Locate the API route configuration or server logs to verify the /forgot-password endpoint is accessible without authentication
    Affected if The endpoint is publicly accessible without authentication requirements
  3. Check for rate limiting on authentication endpoints
    Inspect the Flowise server configuration or middleware settings for rate-limit rules applied to the forgot-password endpoint
    Affected if No rate limiting is configured on the forgot-password endpoint
  4. Verify endpoint response format
    Send a POST request to the forgot-password endpoint with a test email address and examine the HTTP response body for user object data (user ID, name, account status, timestamps) rather than a generic message
    Affected if The endpoint returns full user object data including PII instead of a generic success/failure message

A user is affected if Flowise version is before 3.0.13 AND the forgot-password endpoint is exposed without rate limiting and returns user object data in responses.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Flowise 3.0.13 or later which addresses the improper information disclosure. As a temporary measure, implement rate limiting and request logging on the forgot-password endpoint to detect enumeration attempts.

Recommended fix High confidence

Flowise 3.0.13 or later

  1. 1. Identify the current Flowise installation version by checking the package.json or running the application with --version flag
  2. 2. If running a version before 3.0.13, plan for upgrade to version 3.0.13 or later
  3. 3. Backup the current application data and configuration files before upgrading
  4. 4. For Docker deployments: pull the latest image or specifically pull flowise version 3.0.13
  5. 5. For npm installations: run 'npm install [email protected]' or 'npm install flowise@latest'
  6. 6. For docker-compose deployments: update the image tag to '3.0.13' or 'latest' in docker-compose.yml and recreate containers
  7. 7. After upgrade, verify the /api/v1/account/forgot-password endpoint no longer returns full user objects (it should only return a generic success/failure message)
  8. 8. Test the forgot-password functionality to ensure it still works correctly for legitimate users
Caveat Review release notes for 3.0.13 to check for any breaking changes in configuration or API behavior

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56267 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-56267 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data