dbcve.org
Langflow DesktopApplication · Langflow

CVE-2026-4503

HIGH · 7.5 CVSS v3.1 Published 2026-04-30
Fix available
A fix is available. Upgrade to after 1.8.4 or later.
See remediation →
84/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
IBM Langflow Desktop 1.0.0 through 1.8.4 Langflow could allow an unauthenticated user to view other users' images due to an indirect object reference through a user-controlled key.

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.0.0 through 1.8.4 contains an Insecure Direct Object Reference (IDOR) vulnerability allowing unauthenticated attackers to access arbitrary user images by manipulating a user-controlled key parameter in image retrieval endpoints, resulting in unauthorized information disclosure.

MitigationImplement proper authorization checks ensuring users can only access resources belonging to their own account, and validate object references against the authenticated user's session before returning any content.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Confirm IBM Langflow Desktop installation
    Identify if IBM Langflow Desktop application is installed. Check for the application executable, installation directory, or running process named 'langflow' or 'Langflow Desktop'.
    Affected if The application is IBM Langflow Desktop on the system.
  2. Determine installed version
    Run the command to check the installed version, such as 'langflow --version', checking the application metadata, or inspecting the installed package version. Compare your version against the affected range 1.0.0 to 1.8.4.
    Affected if Installed version is between 1.0.0 and 1.8.4 inclusive.
  3. Verify image retrieval functionality exists
    Inspect the application for image retrieval endpoints or API routes that handle user image requests. Look for endpoints that accept a user-controlled key parameter for image access.
    Affected if Image retrieval endpoints accepting user-controlled key parameters are present in the application.
  4. Check if image storage is accessible
    Examine the application's data directories and file storage locations where user images are stored. Verify if the storage mechanism relies on direct object references without proper authorization checks.
    Affected if User images are stored in a manner that allows direct object reference through URL parameters without authorization validation.

The environment is affected if IBM Langflow Desktop version 1.0.0 through 1.8.4 is installed and the application exposes image retrieval endpoints that accept user-controlled key parameters for accessing user images without authorization validation.

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

Implement proper authorization checks ensuring users can only access resources belonging to their own account, and validate object references against the authenticated user's session before returning any content.

Recommended fix Moderate confidence

Langflow Desktop >= 1.8.5

  1. 1. Backup all Langflow Desktop data and configurations before upgrading
  2. 2. Uninstall the current version of Langflow Desktop (versions 1.0.0 through 1.8.4)
  3. 3. Download Langflow Desktop version 1.8.5 or later from the official Langflow repository (https://github.com/langflow-ai/Langflow)
  4. 4. Install the upgraded version following standard installation procedures
  5. 5. Verify that the application starts successfully and test that image access controls are functioning properly
  6. 6. Review application logs to confirm no IDOR-related errors persist
Caveat Review release notes for any breaking changes between 1.8.4 and 1.8.5; ensure custom integrations or workflows remain compatible

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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