dbcve.org
Langflow DesktopApplication · Langflow

CVE-2026-4502

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-30
Fix available
A fix is available. Upgrade to after 1.8.4 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
IBM Langflow Desktop 1.2.0 through 1.8.4 Langflow could allow an authenticated attacker to traverse directories on the system. An attacker could send a specially crafted URL request containing "dot dot" sequences (/../) to write arbitrary files on the system.

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

IBM Langflow Desktop versions 1.2.0 through 1.8.4 contains a path traversal vulnerability that allows authenticated attackers to use 'dot dot' sequences (/../) in URL requests to write arbitrary files to locations outside the web root folder. This occurs due to insufficient input validation on file path parameters.

MitigationUpdate to a patched version of IBM Langflow Desktop when available. Until then, restrict administrative access to trusted users only and implement strict input validation/sanitization on all file path parameters to reject sequences containing '../'.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Langflow DesktopApplication
Affected:>= 1.2.0, <= 1.8.4

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. Verify Langflow Desktop version
    Locate the installed Langflow Desktop application and determine its version number (typically via application metadata, 'about' dialog, or package information)
    Affected if The installed version is 1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.3.0, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.3.6, 1.3.7, 1.3.8, 1.3.9, 1.3.10, 1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.4.7, 1.5.0, 1.5.1, 1.5.2, 1.5.3, 1.5.4, 1.5.5, 1.5.6, 1.5.7, 1.5.8, 1.5.9, 1.5.10, 1.5.11, 1.5.12, 1.5.13, 1.6.0, 1.6.
  2. Confirm web server component is active
    Determine if the Langflow Desktop web server or API service is currently running and accepting HTTP requests
    Affected if The web server component is running and network-accessible (local or remote)
  3. Inspect authentication configuration
    Review the authentication settings for the Langflow Desktop web interface to determine whether user login is required for access
    Affected if Authentication is enabled but the application accepts file path parameters in URL requests without rejecting '../' sequences

You are affected if Langflow Desktop version 1.2.0 through 1.8.4 is installed AND the web server component is active and accessible with authentication enabled.

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
Upgrade available Upgrade to a release after 1.8.4
Interim mitigation

Update to a patched version of IBM Langflow Desktop when available. Until then, restrict administrative access to trusted users only and implement strict input validation/sanitization on all file path parameters to reject sequences containing '../'.

Recommended fix Moderate confidence

Langflow Desktop version 1.8.5 or later (latest stable release)

  1. 1. Backup your current Langflow Desktop installation and any custom flows or data.
  2. 2. Uninstall the current version of Langflow Desktop (versions 1.2.0 through 1.8.4).
  3. 3. Download the latest version of Langflow Desktop from the official IBM Langflow distribution channel.
  4. 4. Install the new version following the standard installation procedure.
  5. 5. After installation, verify the application runs correctly and test that the path traversal vulnerability is no longer present.
  6. 6. Re-import any previously saved flows or configurations if needed.
Caveat Review release notes for any breaking changes between your current version and the new version, particularly regarding API changes or flow migration requirements

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

Fix this in Langflow Desktop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,460
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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