Quick answers
- Is CVE-2026-33760 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-33760 being exploited in the wild.
- How severe is CVE-2026-33760?
- High severity, with a CVSS score of 8.8, published 23 June 2026.
- Which products and versions are affected?
- langflow (PyPI) ECOSYSTEM:introduced=0,fixed=1.9.0.
- Is there a fix for CVE-2026-33760?
- Yes. langflow (PyPI): upgrade to 1.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-33760 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-33760?
- Check whether you run langflow (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- langflow (PyPI): upgrade to 1.9.0 or later
pip install "langflow>=1.9.0"
Technical details
Langflow's `/api/v1/monitor` router fails to perform ownership validation across seven different endpoints (GET, PUT, PATCH, and DELETE). While the application correctly implements ownership checks in one specific endpoint, the vulnerable endpoints in `monitor.py` accept `flow_id`, `message_id`, or `session_id` parameters without verifying that the `current_user` owns the associated resource. An authenticated attacker can exploit this to perform unauthorized CRUD operations on messages, sessions, build artifacts, and LLM transaction logs. The vulnerability is classified as IDOR/BOLA (Broken Object Level Authorization) and is resolved in version 1.9.0.
Affected products
- langflow-ai Langflow < 1.9.0
Identifiers
- CVE-2026-33760
- GHSA-9c59-2mvc-vfr8
- PYSEC-2026-242
Timeline
- 2026-06-11: advisory: GitHub Security Advisory published
- 2026-06-23: disclosed: NVD publication date