dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-56273

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

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.1.0 contains a path traversal vulnerability in Faiss and SimpleStore vector store implementations that accept unsanitized basePath parameters from authenticated users. Attackers with valid API tokens can write vector store data to arbitrary filesystem locations, potentially enabling code execution or data exfiltration.

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

Flowise before version 3.1.0 has a path traversal vulnerability in the Faiss and SimpleStore vector store implementations. The basePath parameter is not sanitized before being used in file operations, allowing authenticated users with valid API tokens to write vector store data to arbitrary filesystem locations outside the intended directory.

MitigationUpgrade to Flowise 3.1.0 or later which includes proper path sanitization. If immediate upgrade is not feasible, implement input validation to ensure basePath resolves to an expected directory and does not contain traversal sequences like '..'.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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
    Run 'npm list flowise' or check package.json, or query the Flowise API endpoint /api/v1/version if available
    Affected if Version is before 3.1.0 (version check returns something less than 3.1.0 or no version found indicates likely older install)
  2. Confirm Faiss or SimpleStore vector store is in use
    Review Flowise application configurations, stored flow definitions, or database for vector store nodes that use Faiss or SimpleStore implementations
    Affected if Any flow or configuration references Faiss or SimpleStore as the vector store type
  3. Inspect basePath configuration
    Examine Flowise configuration files, environment variables, or the vector store node settings in saved flows for the basePath parameter
    Affected if basePath is set to a user-controlled location or contains path traversal sequences, or basePath is not explicitly set (may default to vulnerable behavior)
  4. Verify API token authentication is enabled
    Check Flowise security configuration (auth settings in config file or environment variables like FLOWISE_USERNAME/FLOWISE_PASSWORD, or API key settings)
    Affected if Authentication is enabled (the vulnerability requires valid API tokens, so this is a prerequisite condition)
  5. Review filesystem write permissions
    Check the process user running Flowise has write access to directories outside the intended vector store directory
    Affected if Flowise process runs with elevated privileges or has broad filesystem write access beyond the intended data directory

A user is affected if Flowise version is below 3.1.0 AND Faiss or SimpleStore vector store is in use with a configurable basePath, and the installation has authentication enabled (which enables the attack vector).

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.1.0 or later which includes proper path sanitization. If immediate upgrade is not feasible, implement input validation to ensure basePath resolves to an expected directory and does not contain traversal sequences like '..'.

Recommended fix High confidence

Flowise 3.1.0

  1. 1. Back up your current Flowise installation and configuration
  2. 2. Consult the official Flowise release notes or changelog to review changes in version 3.1.0
  3. 3. Upgrade Flowise to version 3.1.0 using your installation method (npm, Docker, or other)
  4. 4. Verify the upgrade was successful by checking the version number
  5. 5. Test that vector store functionality (Faiss and SimpleStore) works correctly with the new version
  6. 6. If using API tokens, ensure they continue to work as expected after upgrade
Caveat No specific breaking changes documented in the provided description; review release notes for full details

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56273 — 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-56273 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