dbcve.org
LangflowApplication

CVE-2026-0772

HIGH · 7.5 CVSS v3.0 Published 2026-01-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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
Langflow Disk Cache Deserialization of Untrusted Data Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Langflow. Authentication is required to exploit this vulnerability. The specific flaw exists within the disk cache service. The issue results from the lack of proper validation of user-supplied data, which can result in deserialization of untrusted data. An attacker can leverage this vulnerability to execute code in the context of the service account. Was ZDI-CAN-27919.

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

Langflow contains a deserialization vulnerability in its disk cache service where user-supplied data is deserialized without proper validation. An authenticated attacker can exploit this to achieve remote code execution in the context of the service account by sending specially crafted serialized data to the disk cache.

MitigationImplement safe deserialization practices: validate all cached data before deserialization, use allowlist approaches for deserializable types, or replace pickle-based serialization with safer formats like JSON. Apply principle of least privilege to the service account.

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

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

CVSS:3.0/AV:N/AC:H/PR:L/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. Identify Langflow installation and version
    Run 'pip show langflow' or check the running service version. On Linux, also check /opt or /usr/local/lib for Langflow installations. If running as a service, check the process list for langflow processes.
    Affected if The installed version is exactly 1.5.0
  2. Locate and inspect the disk cache configuration
    Check Langflow configuration files (typically in /etc/langflow/, ~/.config/langflow/, or the working directory) for cache-related settings. Look for 'cache', 'disk_cache', 'pickle', or 'serialization' configuration keys.
    Affected if Cache configuration exists and specifies disk-based caching using pickle serialization
  3. Verify if disk cache service is active
    Examine the Langflow runtime configuration or logs to determine if the disk cache feature is enabled. Check for cache directory creation (commonly in /tmp/langflow_cache, /var/cache/langflow, or similar).
    Affected if Disk cache service is enabled and the cache directory is being used
  4. Check authentication exposure
    Review whether Langflow's API or web interface is accessible to authenticated users. Verify if anonymous access is permitted to cache-related endpoints.
    Affected if An authenticated user can send requests to Langflow services that utilize the disk cache

A system is affected if Langflow version 1.5.0 is running with disk-based cache enabled, allowing authenticated users to interact with the vulnerable deserialization component.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement safe deserialization practices: validate all cached data before deserialization, use allowlist approaches for deserializable types, or replace pickle-based serialization with safer formats like JSON. Apply principle of least privilege to the service account.

Fix this in Langflow Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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