Langflow Flaws Enable Cross-Tenant Access and Fuel Cryptominer Intrusions
Multiple vulnerabilities in Langflow have exposed AI application deployments to both account-to-account abuse and active compromise. CVE-2026-33760 affects versions before 1.9.0 and allows authenticated users to read, modify, rename, or delete other users’ messages, sessions, build artifacts, and LLM transaction logs through seven /api/v1/monitor endpoints that fail to enforce ownership checks. A separate flaw, CVE-2026-55255, affects versions before 1.9.2 and lets an authenticated attacker execute another user’s flow through the /api/v1/responses endpoint by supplying a victim flow_id, giving the issue a critical CVSS 9.9 rating.
At the same time, defenders are tracking a cryptocurrency-mining campaign exploiting CVE-2026-33017, an unauthenticated remote code execution bug in Langflow, to compromise exposed instances and deploy Monero miners. Threat research says the malware disables security controls, installs persistence, and can enable lateral movement through reused SSH keys; observed infrastructure includes 83.142.209.214 and 94.156.64.241. Organizations running Langflow are being urged to upgrade to 1.9.0 and 1.9.2 or later as applicable, verify access-control enforcement, restrict public exposure of Langflow services, and treat signs of miner activity or unauthorized flow execution as a significant incident.
Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
3 events from the most recent confirmed update back to the earliest known activity.
Cryptomining campaign exploits Langflow CVE-2026-33017
A cryptocurrency-mining campaign was reported exploiting CVE-2026-33017, an unauthenticated remote code execution flaw in Langflow, against exposed AI application endpoints. The activity disabled host security controls, deployed a custom miner, established persistence, and used infrastructure including 83.142.209.214 and 94.156.64.241.
Langflow fixes /api/v1/responses IDOR in version 1.9.2
Langflow fixed CVE-2026-55255 in version 1.9.2. The vulnerability in the /api/v1/responses endpoint allowed an authenticated attacker to execute another user's flow by supplying the victim's flow ID.
Langflow fixes monitor API IDOR/BOLA in version 1.9.0
Langflow addressed CVE-2026-33760 in version 1.9.0. The flaw affected seven /api/v1/monitor endpoints that failed to enforce ownership checks, allowing authenticated users to access, modify, rename, or delete other users' resources.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
3 references tracked. Mallory keeps watching after this page renders.
From Langflow to Monero: Inside CVE-2026-33017 Cryptominer | Community Portal | Gurucul
community.gurucul.com
Open sourceCVE-2026-33760 - Langflow: IDOR/BOLA in Monitor API - Missing Ownership Enforcement on 7 Endpoints
cvefeed.io
Open sourceCVE-2026-55255 - Langflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's Flow
cvefeed.io
Open sourceSee the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Related stories
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Actively Exploited Langflow RCE Exposed AI Pipeline Secrets and Triggered CISA KEV Listing
Threat actors rapidly exploited **CVE-2026-33017**, a critical unauthenticated remote code execution flaw in Langflow’s public flow build endpoint, allowing arbitrary Python code to reach an unsandboxed `exec()` path with a single crafted request. The bug affects Langflow versions prior to **1.9.0** and stems from the `POST /api/v1/build_public_tmp/{flow_id}/flow` endpoint accepting attacker-controlled flow data through an optional parameter. Researchers and vendor advisories said the issue is distinct from **CVE-2025-3248** because the vulnerable endpoint is intentionally public, meaning the fix required removing attacker-supplied flow data from that execution path rather than simply adding authentication. Sysdig and other researchers reported exploitation beginning within about **20 hours** of disclosure, with attackers scanning for exposed instances, validating code execution, reading files such as `.env`, `.db`, and `/etc/passwd`, stealing credentials, API keys, and database secrets, and attempting follow-on payload delivery from infrastructure including `173.212.205[.]251:8443`. The severity prompted **CISA** to add the flaw to its **Known Exploited Vulnerabilities** catalog and order federal agencies to remediate by **April 8, 2026** or discontinue use if they could not secure affected systems. Security guidance across the reports urged organizations to upgrade to **Langflow 1.9.0 or later**, restrict or remove internet exposure of the vulnerable endpoint, monitor outbound connections, and rotate secrets if compromise is suspected.
Jun 8, 2026
Langflow fixes IDOR letting authenticated users execute other users’ flows
Langflow disclosed a high-impact insecure direct object reference vulnerability, tracked as **`GHSA-qrpv-q767-xqq2`**, that allowed any authenticated user on affected deployments to access and execute another user’s flow through the **`/api/v1/responses`** endpoint. The flaw affected pip package versions earlier than **`1.9.1`** and stemmed from backend logic that resolved flows by UUID without verifying ownership, enabling an attacker to submit a victim’s flow UUID and receive the resulting output. Successful exploitation could expose sensitive data processed by the victim’s flow and consume the victim’s compute resources. The fix, merged in PR **`#12832`**, added ownership checks for both UUID- and endpoint-name-based flow lookups and changed unauthorized access handling to return **`404`** instead of **`403`** to avoid revealing whether a target flow exists. Langflow also hardened related routes, including **`/api/v1/run`**, **`/api/v1/run/session`**, and **`/api/v1/run/advanced`**, to close similar unscoped dependency patterns, and added regression tests covering cross-user access, malformed **`user_id`** inputs, and the reported proof of concept. Users are advised to upgrade to **`1.9.1`** or later.
Jun 20, 2026
Unpatched Langflow Path Traversal Flaw Exploited for Unauthenticated RCE
Attackers are actively exploiting **CVE-2026-5027**, a high-severity path traversal vulnerability in the open-source AI application platform **Langflow**, to write files to arbitrary locations on target systems and potentially achieve remote code execution. The flaw affects the `POST /api/v2/files` endpoint, where the `filename` parameter is not properly sanitized, and exploitation is made more severe by Langflow's default unauthenticated auto-login behavior, which lets attackers obtain a valid session token with a single unauthenticated request. VulnCheck reported observed attacks writing apparent test files to victim hosts, while Tenable identified the issue and assigned it a **CVSS 8.8** score. Internet exposure increases the risk: Censys data indicates about **7,000** Langflow instances are reachable online, with the largest concentration in North America. The exploitation report also fits a broader pattern of sustained attacker interest in Langflow, with other vulnerabilities including **`CVE-2026-0770`**, **`CVE-2026-21445`**, **`CVE-2026-33017`**, and **`CVE-2025-34291`** also reported as exploited in 2026; the last has been linked in public reporting to the Iranian state-backed group **MuddyWater**. Separately, a newly disclosed flaw in **Roxy-WI** (**`CVE-2026-45556`**) shows a similar arbitrary file-write-to-RCE pattern on managed load balancers, but no public patch was available at publication.
Jun 11, 2026