CVE-2026-33760

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Langflow is a tool for building and deploying AI-powered agents and workflows. Prior to 1.9.0, Langflow's /api/v1/monitor router exposes 7 endpoints that perform read, write, and delete operations on user-owned resources — messages, sessions, build artifacts, and LLM transaction logs — without verifying that the authenticated requester owns the targeted resource. Any authenticated user can read, modify, rename, or permanently delete another user's data by supplying the target's resource ID or flow_id. This is a classic IDOR/BOLA vulnerability. Notably, the same source file (monitor.py) contains one correctly-implemented endpoint that uses an ownership check, demonstrating the correct pattern was known but inconsistently applied. This vulnerability is fixed in 1.9.0.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
20.9%
KEV
Not listed

Published

June 16, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Jun 23, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

IDOR/BOLA in Monitor API — Missing Ownership Enforcement on 7 Endpoints · Advisory · langflow-ai/langflow · GitHub

https://github.com/langflow-ai/langflow/security/advisories/GHSA-9c59-2mvc-vfr8

Vendor Advisories for CVE-2026-33760(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
langflow0.0.31 ... 1.8.4 (293 versions)1.9.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 58× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 23:12 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:22 UTCEG score recompute
  7. 2026-07-05 14:16 UTCEG score recompute
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-05 02:11 UTCEG score recompute
  10. 2026-07-04 14:06 UTCEG score recompute
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-04 01:55 UTCEG score recompute
  13. 2026-07-03 13:48 UTCEG score recompute
  14. 2026-07-03 01:28 UTCEG score recompute
  15. 2026-07-02 13:23 UTCEG score recompute
  16. 2026-07-02 01:06 UTCEG score recompute
  17. 2026-07-01 15:06 UTCEPSS rescore
  18. 2026-07-01 13:02 UTCEG score recompute
  19. 2026-07-01 00:55 UTCEG score recompute
  20. 2026-06-30 23:22 UTCEPSS rescore
  21. 2026-06-30 12:51 UTCEG score recompute
  22. 2026-06-30 00:25 UTCEG score recompute
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 12:21 UTCEG score recompute
Show 33 more
  1. 2026-06-29 00:17 UTCEG score recompute
  2. 2026-06-28 14:07 UTCEPSS rescore
  3. 2026-06-28 14:07 UTCEPSS rescore
  4. 2026-06-28 12:12 UTCEG score recompute
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-28 04:56 UTCEPSS rescore
  7. 2026-06-28 00:05 UTCEG score recompute
  8. 2026-06-27 12:00 UTCEG score recompute
  9. 2026-06-27 03:08 UTCEPSS rescore
  10. 2026-06-26 23:54 UTCEG score recompute
  11. 2026-06-26 11:50 UTCEG score recompute
  12. 2026-06-25 20:34 UTCEG score recompute
  13. 2026-06-25 13:49 UTCEPSS rescore
  14. 2026-06-25 13:49 UTCEPSS rescore
  15. 2026-06-25 08:29 UTCEG score recompute
  16. 2026-06-24 20:25 UTCEG score recompute
  17. 2026-06-24 14:05 UTCEPSS rescore
  18. 2026-06-24 08:21 UTCEG score recompute
  19. 2026-06-23 20:16 UTCEG score recompute
  20. 2026-06-23 08:11 UTCEG score recompute
  21. 2026-06-22 20:06 UTCEG score recompute
  22. 2026-06-22 07:56 UTCEG score recompute
  23. 2026-06-21 19:38 UTCEG score recompute
  24. 2026-06-21 07:34 UTCEG score recompute
  25. 2026-06-20 19:27 UTCEG score recompute
  26. 2026-06-20 06:30 UTCEG score recompute
  27. 2026-06-19 18:22 UTCEG score recompute
  28. 2026-06-19 06:17 UTCEG score recompute
  29. 2026-06-18 18:13 UTCEG score recompute
  30. 2026-06-18 06:04 UTCEG score recompute
  31. 2026-06-17 17:57 UTCEG score recompute
  32. 2026-06-17 05:51 UTCEG score recompute
  33. 2026-06-16 17:46 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-33760?
CVE-2026-33760 is a high vulnerability published on June 16, 2026. Langflow is a tool for building and deploying AI-powered agents and workflows. Prior to 1.9.0, Langflow's /api/v1/monitor router exposes 7 endpoints that perform read, write, and delete operations on user-owned resources — messages, sessions, build artifacts, and LLM transaction logs — without…
When was CVE-2026-33760 disclosed?
CVE-2026-33760 was first published in the National Vulnerability Database on June 16, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33760 actively exploited?
CVE-2026-33760 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-33760?
CVE-2026-33760 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-33760?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33760, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33760

Explore →

Is Your Infrastructure Affected by CVE-2026-33760?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs