dbcve.org
LangflowApplication

CVE-2026-7524

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-27
Fix available
A fix is available. Upgrade to after 1.9.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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 OSS 1.0.0 through 1.9.1 could allow remote code execution due to improper validation of symbolic links during archive extraction.

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 versions 1.0.0 through 1.9.1 contains a path traversal vulnerability during archive extraction where symbolic links are not properly validated, allowing attackers to write files to arbitrary locations on the filesystem and achieve remote code execution.

MitigationUpgrade to a patched version of IBM Langflow. If immediate patching is not possible, implement strict validation of symbolic links and path traversal checks before extracting any archives, ensuring extracted files remain within the intended target directory.

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
LangflowApplication
Affected:>= 1.0.0, <= 1.9.1

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

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

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. Determine installed Langflow version
    Run 'pip show langflow' or 'pip list | grep langflow' to retrieve the installed package version
    Affected if Version is 1.0.0 through 1.9.1 inclusive
  2. Verify archive extraction feature is in use
    Review Langflow deployment for archive upload/import functionality - check for endpoints or code that handle .zip or .tar file uploads (look for zipfile/tarfile module usage in the codebase)
    Affected if Archive extraction capability is enabled and accessible to users or automated processes
  3. Check for untrusted archive processing
    Audit logs or access records for any uploaded archives being extracted by the Langflow application, particularly in flow/agent import features
    Affected if Untrusted archives have been uploaded and extracted in the environment

Environment is affected if installed Langflow version is between 1.0.0 and 1.9.1 and archive upload/extraction functionality is present and used.

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.

From vendor data
Upgrade available Upgrade to a release after 1.9.1
Interim mitigation

Upgrade to a patched version of IBM Langflow. If immediate patching is not possible, implement strict validation of symbolic links and path traversal checks before extracting any archives, ensuring extracted files remain within the intended target directory.

Fix this in Langflow Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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