Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
UnratedPublic exploit

Langflow /api/v1/responses Cross-Tenant IDOR

IdentifiersCVE-2026-55255CWE-639

CVE-2026-55255 is a critical insecure direct object reference vulnerability in Langflow affecting versions prior to 1.9.2. The flaw is in the POST /api/v1/responses endpoint, where the supplied model field can reference a flow UUID. Langflow resolves flows by UUID via get_flow_by_id_or_endpoint_name without enforcing a user_id ownership check on that code path. As a result, an authenticated attacker who knows a victim’s flow ID can submit requests that cause execution of flows belonging to another user. Available reporting also indicates the endpoint_name lookup path enforces ownership checks, and only the UUID-based resolution path is vulnerable. In observed exploitation, attackers first enumerated flow IDs via GET /api/v1/flows/ and then replayed those IDs to /api/v1/responses to trigger victim flows.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows cross-user or cross-tenant execution of victim-owned Langflow flows using the victim flow’s embedded configuration and credentials. This can expose secrets such as API keys, permit unauthorized access to data processed by the victim workflow, consume victim resources, and compromise confidentiality, integrity, and availability within shared or managed Langflow environments. The issue is especially serious in multi-tenant deployments because it enables quiet lateral access across tenant boundaries through otherwise legitimate-looking API calls.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by restricting Langflow access to trusted authenticated users, minimizing or eliminating internet exposure, limiting disclosure of flow identifiers, and closely monitoring for anomalous POST /api/v1/responses requests that reference unexpected flow IDs or trigger cross-user execution. Review logs for prior enumeration of GET /api/v1/flows/ followed by response-execution requests, and rotate any secrets that may have been exposed through unauthorized flow execution.

Remediation

Patch, then assume compromise.

Upgrade Langflow to version 1.9.2 or later, which fixes the vulnerable access-control behavior in /api/v1/responses. After upgrading, verify the deployed version and confirm that ownership validation is enforced for UUID-based flow resolution in get_flow_by_id_or_endpoint_name. If operating multiple instances or managed environments, ensure all tenants and nodes are updated consistently.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LangflowLangflowapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity4

Community discussion across Reddit, Mastodon, and other social sources.