dbcve.org
Langflow DesktopApplication · Langflow

CVE-2026-3340

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 →
74/100
Remediation priority · Elevated
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
IBM Langflow Desktop 1.0.0 through 1.8.4 IBM Langflow is vulnerable to server-side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks.

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 · moderate confidence

IBM Langflow Desktop versions 1.0.0 through 1.8.4 is vulnerable to server-side request forgery (SSRF). An authenticated attacker can abuse the application's request-handling functionality to send arbitrary HTTP requests from the server, enabling internal network enumeration and potentially pivoting to internal services.

MitigationUpgrade to a version beyond 1.8.4 if available, and implement network segmentation to restrict outbound connections from the server. Additionally, apply input validation to restrict URLs/hosts that the application can access.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 Langflow Desktop installation and version
    Locate the Langflow Desktop application and retrieve its version number. On Windows, check Add/Remove Programs or the application directory. On macOS, check /Applications or the app bundle info. On Linux, check installed packages or the application directory.
    Affected if The installed version falls within 1.0.0 through 1.8.4 inclusive.
  2. Confirm authentication is enabled
    Check the application's configuration files (typically in the user data directory or config folder) for authentication settings. Look for whether login/registration is required to access the application interface or API.
    Affected if Authentication is not properly configured or enforced, making the SSRF endpoint accessible to unauthenticated attackers.
  3. Verify network accessibility
    Determine if the Langflow Desktop application has outbound network access. Check firewall rules, proxy settings, or network configuration that controls the application's ability to make HTTP requests.
    Affected if The server can make outbound HTTP requests, allowing the SSRF vulnerability to be exploited for internal network enumeration.

A user is affected if they have Langflow Desktop version 1.0.0 to 1.8.4 running with authentication enabled but the application can make outbound network requests.

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

Upgrade to a version beyond 1.8.4 if available, and implement network segmentation to restrict outbound connections from the server. Additionally, apply input validation to restrict URLs/hosts that the application can access.

Recommended fix Low confidence

Latest available IBM Langflow Desktop version beyond 1.8.4

  1. 1. Identify the current installed version of IBM Langflow Desktop by checking the application or using command-line tools
  2. 2. Download the latest version of IBM Langflow Desktop from the official IBM sources
  3. 3. Backup any existing configurations, flows, or user data before upgrading
  4. 4. Uninstall the current version (1.0.0 through 1.8.4)
  5. 5. Install the latest available version which should contain the SSRF vulnerability fix
  6. 6. Verify the installation was successful and the application runs without errors
  7. 7. Test that the authenticated functionality works as expected post-upgrade
Caveat Review IBM release notes for any breaking changes between your current version and the target version

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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