IBM Langflow OSS 1.0.0 through 1.8.4 contains multiple broken access control vulnerabilities in its file handling API that allow unauthorized access to user files.The /api/v1/files/images/{flow_id}/{file_name} endpoint does not enforce authentication or authorization checks, allowing unauthenticated remote attackers to retrieve image files associated with any flow by specifying a valid flow_id and file_name.Additionally, the /api/v1/files/download/{flow_id}/{file_name} endpoint requires authentication but fails to properly validate ownership of the requested resource. As a result, an authenticated user can access files belonging to other users by supplying arbitrary identifiers, leading to an authorization bypass (IDOR).Successful exploitation may result in unauthorized disclosure of sensitive data, including files stored in private flows. This issue breaks tenant isolation in multi-user deployments.
CVE-2026-10700
Score 6.5 from GitHub Security Advisory published 2026-07-30. a secondary CVSS source baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(high)
- EG Risk
- 29(Track)EG Risk 29/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 32%
- KEV
- Not listed
Published
July 30, 2026
Last Modified
August 4, 2026
Advisory Details (1)
Auto-updated Jul 30, 2026Security Bulletin: Broken Access Control Vulnerabilities in Langflow 1.0.0 - 1.8.4 File Handling API Allowed Unauthorized Access to User Files
https://www.ibm.com/support/pages/node/7279675Vendor Advisories for CVE-2026-10700(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 20× in last 7d / 64× 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.
- 2026-08-20 18:41 UTCGHSA enrichment
- 2026-08-19 20:13 UTCEG score recompute
- 2026-08-19 20:13 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 21:45 UTCEG score recompute
- 2026-08-18 21:45 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 23:11 UTCEG score recompute
- 2026-08-17 23:11 UTCGHSA enrichment
- 2026-08-17 00:42 UTCEG score recompute
- 2026-08-17 00:42 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-16 02:13 UTCGHSA enrichment
- 2026-08-15 03:46 UTCEG score recompute
- 2026-08-15 03:46 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 05:18 UTCEG score recompute
- 2026-08-14 05:18 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 06:50 UTCEG score recompute
- 2026-08-13 06:50 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 08:20 UTCEG score recompute
- 2026-08-12 08:20 UTCGHSA enrichment
Show 39 moreShow fewer
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 09:51 UTCEG score recompute
- 2026-08-11 09:51 UTCGHSA enrichment
- 2026-08-10 23:59 UTCEPSS rescore
- 2026-08-10 11:24 UTCEG score recompute
- 2026-08-10 11:24 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 12:55 UTCEG score recompute
- 2026-08-09 12:55 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 14:27 UTCEG score recompute
- 2026-08-08 14:27 UTCGHSA enrichment
- 2026-08-07 15:58 UTCGHSA enrichment
- 2026-08-06 17:30 UTCEG score recompute
- 2026-08-06 17:30 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 19:02 UTCGHSA enrichment
- 2026-08-04 20:34 UTCGHSA enrichment
- 2026-08-04 17:11 UTCEG score recompute
- 2026-08-04 17:11 UTCGHSA enrichment
- 2026-08-04 15:09 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-03 18:43 UTCEG score recompute
- 2026-08-03 18:43 UTCGHSA enrichment
- 2026-08-03 10:35 UTCEPSS rescore
- 2026-08-02 20:15 UTCEG score recompute
- 2026-08-02 20:15 UTCGHSA enrichment
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-01 21:46 UTCEG score recompute
- 2026-08-01 21:46 UTCGHSA enrichment
- 2026-08-01 04:15 UTCEPSS rescore
- 2026-07-31 23:18 UTCEG score recompute
- 2026-07-31 23:17 UTCGHSA enrichment
- 2026-07-31 18:05 UTCEG score recompute
- 2026-07-31 18:05 UTCGHSA enrichment
- 2026-07-30 19:30 UTCEG score recompute
- 2026-07-30 17:22 UTCEG score recompute
- 2026-07-30 17:20 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS p94CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS p94CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS p97CRITICAL
- CVE-2019-13360EG 9.8EPSS p98CRITICAL
- CVE-2019-12866EG 9.8CRITICAL
- CVE-2019-9756EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-10700?
When was CVE-2026-10700 disclosed?
Is CVE-2026-10700 actively exploited?
What is the CVSS score of CVE-2026-10700?
How do I remediate CVE-2026-10700?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-10700
Is Your Infrastructure Affected by CVE-2026-10700?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.