UnratedPublic exploit

IDOR/BOLA in Langflow Monitor API

IdentifiersCVE-2026-33760CWE-639

CVE-2026-33760 is a high-severity insecure direct object reference / broken object level authorization vulnerability in Langflow affecting versions prior to 1.9.0. The flaw is in the /api/v1/monitor router, where seven endpoints perform read, update, rename, and delete operations on user-owned resources without verifying that the authenticated requester actually owns the targeted object. Affected resources include messages, sessions, build artifacts, and LLM transaction logs. By supplying another user's resource ID or flow_id, any authenticated user can access or manipulate data across tenant or user boundaries. The advisory notes that the same monitor.py file contains one endpoint with a correct ownership check, indicating the secure authorization pattern existed but was not consistently applied across the affected endpoints.

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.

Start free trial

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 an authenticated attacker to violate confidentiality, integrity, and availability of other users' data. An attacker can read sensitive messages, sessions, build artifacts, and LLM transaction logs; modify or rename other users' resources; and permanently delete targeted data. In multi-user deployments, this enables cross-user or cross-tenant data exposure and tampering, including access to potentially sensitive LLM prompts, responses, and workflow-related artifacts.

Mitigation

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

If immediate patching is not possible, reduce exposure by limiting Langflow to single-user or tightly trusted-user deployments, disabling open or self-service registration, and restricting access to the affected monitor API endpoints via reverse proxy, API gateway, or network ACL controls. Apply strong authentication, network segmentation, and least-privilege access controls to minimize the number of authenticated users who can reach the vulnerable endpoints.

Remediation

Patch, then assume compromise.

Upgrade Langflow to version 1.9.0 or later, which fixes the vulnerability. Ensure all affected /api/v1/monitor endpoints enforce object-level authorization by validating that the requested resource is owned by, or otherwise authorized for, the authenticated user before permitting read, update, rename, or delete operations. Review similar endpoints for consistent ownership enforcement tied to the authenticated user's identity, including Flow.user_id or equivalent authorization checks.

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.

ACTIVITY FEED

Recent activity

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

2 SOURCESView more in app

cvefeed high severityNews

Jun 23, 2026

CVE-2026-33760 - Langflow: IDOR/BOLA in Monitor API - Missing Ownership Enforcement on 7 Endpoints

An insecure direct object reference / broken object level authorization vulnerability in Langflow's Monitor API that allows any authenticated user to read, modify, rename, or permanently delete another user's resources by supplying resource IDs or flow_id values.

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.

Start free trial

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 activity1

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

EXTERNAL REFERENCES

MITRE CVE

cve.org · CVE-2026-33760

NVD

nvd.nist.gov/vuln/detail/CVE-2026-33760

MITRE CWE · CWE-639

cwe.mitre.org