dbcve.org
Langflow DesktopApplication · Langflow

CVE-2026-3341

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-11
Fix available
A fix is available. Upgrade to 1.9.3 or later.
See remediation →
60/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.0.0 through 1.9.2 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.9.2 contains a Server-Side Request Forgery (SSRF) vulnerability that allows authenticated users to induce the server to make arbitrary HTTP requests to internal or external resources. This can enable network enumeration, access to internal services, and serve as a pivot point for further attacks.

MitigationUpgrade IBM Langflow Desktop to a version beyond 1.9.2 once available. Additionally, implement strict URL allow-listing and validate all user-supplied URLs server-side to prevent requests to internal network ranges (127.0.0.0/8, 10.0.0.0/8, 192.168.0.0/16, etc.).

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.9.3

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Locate IBM Langflow Desktop installation
    Check common installation directories: Windows typically installs to C:\Program Files\IBM\Langflow or C:\Users\[user]\AppData\Local\Programs\langflow. On macOS, check /Applications folder or ~/Applications. On Linux, check /opt/langflow or /usr/local/lib/langflow.
    Affected if IBM Langflow Desktop is found installed on the system
  2. Determine installed version number
    On Windows, check the version via Control Panel > Programs and Features > IBM Langflow Desktop > Properties, or right-click the executable and view Details. On macOS, right-click the app bundle > Get Info. On Linux, check the version via the installed package metadata or run the application with --version flag if supported.
    Affected if The installed version falls within 1.0.0 through 1.9.2 (inclusive)
  3. Verify authentication is enabled for the web interface
    Langflow Desktop exposes a web interface. Check if user authentication is configured and active. Review configuration files (typically config.yaml, settings.json, or .env in the installation directory) for AUTH_ENABLED, AUTHENTICATION, or LOGIN_REQUIRED settings.
    Affected if Authentication is disabled or not required, making the SSRF reachable without credentials; note that the CVE states authenticated users can exploit, so confirm whether user accounts exist in the system
  4. Check network exposure of Langflow web service
    Review the application's startup configuration or listen address settings (in config files or environment variables) to determine if the web interface binds to 0.0.0.0 (all interfaces) versus 127.0.0.1 (localhost only).
    Affected if The service is exposed on network interfaces accessible beyond localhost, increasing the attack surface for SSRF exploitation

If IBM Langflow Desktop is installed with a version between 1.0.0 and 1.9.2 and the application web interface is accessible (with or without authentication), the environment is affected by this SSRF vulnerability.

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 1.9.3 or later
Fixed in 1.9.3
Interim mitigation

Upgrade IBM Langflow Desktop to a version beyond 1.9.2 once available. Additionally, implement strict URL allow-listing and validate all user-supplied URLs server-side to prevent requests to internal network ranges (127.0.0.0/8, 10.0.0.0/8, 192.168.0.0/16, etc.).

Recommended fix High confidence

1.9.3 or later

  1. 1. Back up your current Langflow Desktop installation and any custom configurations or flows.
  2. 2. Verify your current installed version by checking the application settings or using the application's 'About' section.
  3. 3. Download Langflow Desktop version 1.9.3 or later from the official distribution channel (e.g., GitHub releases, official website, or package manager).
  4. 4. Uninstall the current version of Langflow Desktop following standard uninstallation procedures for your operating system.
  5. 5. Install the downloaded version 1.9.3 or later.
  6. 6. Restore any backed-up custom configurations or flows to the new installation.
  7. 7. Verify the application starts successfully and test that the SSRF vulnerability is mitigated by confirming the fix is applied.

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

Fix this in Langflow Desktop Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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