Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2026-55255: Cross-user workflow execution IDOR in Langflow

Published Jun 23, 2026 · Updated 27 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS8.4High · v3.1
EPSS0.89%60th percentile
CISA KEVYesAdded Jul 7, 2026
In the wildActivePer CISA KEV
Vendor
Langflow
IdentifiersCVE-2026-55255CWE-639 · Authorization Bypass Through…

CVE-2026-55255 is an insecure direct object reference vulnerability in Langflow's OpenAI-compatible Responses API. The get_flow_by_id_or_endpoint_name() helper resolves client-supplied flow UUIDs without verifying ownership by the authenticated requester, unlike its endpoint-name resolution branch. An authenticated user can therefore invoke another user's workflow by supplying its UUID in the model parameter. The workflow executes using the victim's configured credentials and integrations, potentially exposing sensitive data and embedded secrets. The primary affected-version range is Langflow releases before 1.9.1, although some affected-version information extends the range to releases before 1.9.2. Exploitation was observed beginning June 25, 2026, and CISA added the vulnerability to its Known Exploited Vulnerabilities catalog on July 7, 2026.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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

Successful exploitation breaks user and tenant isolation, allowing unauthorized workflow execution, access to sensitive workflow outputs, and consumption of victim resources. Depending on workflow behavior, attackers may extract LLM-provider API keys, cloud credentials, database secrets, or other sensitive information available to the workflow. Exposed credentials can enable downstream access to connected services within their granted permissions. This vulnerability alone does not establish arbitrary operating-system command execution.

Mitigation

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

Until patched, restrict or disable access to the Responses API, limit deployment access to trusted users and networks, and remove unnecessary internet exposure. Monitor for flow identifiers that do not belong to the authenticated requester and unexpected workflow executions. Authentication alone is insufficient because ordinary authenticated users can exploit the flaw.

Remediation

Patch, then assume compromise.

Upgrade to a current supported Langflow release. The ownership-check fix is identified as introduced in 1.9.1, but conflicting affected-version information identifies 1.9.2 as the fixed release; use 1.9.2 or later to cover both stated boundaries. The fix must enforce ownership or equivalent authorization for UUID-based flow resolution as well as endpoint-name-based resolution. Review historical executions for cross-user access and rotate potentially exposed provider keys, cloud credentials, and database secrets.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
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
FAQ

Frequently asked questions

Is CVE-2026-55255 exploited in the wild?
Yes. As of Oct 20, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Jul 7, 2026.
Is there a public exploit for CVE-2026-55255?
Yes. As of Oct 20, 2026, Mallory has reports of a public exploit for CVE-2026-55255.
Is there a patch for CVE-2026-55255?
Upgrade to a current supported Langflow release. The ownership-check fix is identified as introduced in 1.9.1, but conflicting affected-version information identifies 1.9.2 as the fixed release; use 1.9.2 or later to cover both stated boundaries.
What products are affected by CVE-2026-55255?
Langflow.
How severe is CVE-2026-55255?
CVE-2026-55255 has a CVSS v3.1 score of 8.4 (High) and an EPSS score of 0.89% (60th percentile) as of Oct 20, 2026.
Activity feed

Recent activity

110 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
mkd cirtNews · Oct 15, 2026Критичната ранливост во Langflow што овозможува далечинско извршување код се цел на 1.423 обиди за експлоатација забележани преку honeypot-системи | MKD-CIRT | Национален центар за одговор на компјутерски инцидентиUnknownRead more ↗nuclei templates pull requestsNews · Sep 9, 2026Add CVE-2026-55255 template: Langflow cross-user flow IDOR (complete self-contained POC) by mohamed-bashir-dev · Pull Request #17186 · projectdiscovery/nuclei-templates · GitHubAn insecure direct object reference (IDOR) vulnerability in Langflow involving cross-user access to flows by flow ID. The supplied proof-of-concept/template tests whether a user can invoke another user's flow through the Langflow run API endpoint.Read more ↗nuclei templates pull requestsNews · Sep 8, 2026Add CVE-2026-55255 template: Langflow cross-user flow IDOR by mohamed-bashir-dev · Pull Request #17180 · projectdiscovery/nuclei-templates · GitHubAn insecure direct object reference (IDOR) vulnerability in Langflow involving cross-user access to flows by flow identifier, including the API run endpoint.Read more ↗cysecurity newsNews · Sep 2, 2026Attackers Turn Langflow and Rails Flaws Into Entry Points for Credential Probing - CySecurity News - Latest Information Security and Hacking IncidentsAn insecure direct object reference vulnerability used with CVE-2026-33017 in credential-harvesting attacks.Read more ↗
+22 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

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, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity80Community discussion across Reddit, Mastodon, and other social sources.