IBM Langflow OSS 1.0.0 through 1.10.3 contain an authorization bypass vulnerability in the MemoryComponent that allows authenticated users to access chat history of other users via session_id collision. The MemoryComponent.retrieve_messages and store_message methods filter on session_id without validating flow_id or user_id ownership, enabling cross-user information disclosure through multiple authenticated API endpoints including /api/v1/run/*, /api/v1/responses, and /api/v2/workflow/*. This vulnerability only affects multi-user deployments with LANGFLOW_AUTO_LOGIN=False.
CVE-2026-9130
Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-05. a secondary CVSS source baseline 7.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(high)
- EG Risk
- 32(Track)EG Risk 32/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 computedSeverity71% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 7%
- KEV
- Not listed
Published
August 5, 2026
Last Modified
August 7, 2026
Advisory Details (1)
Auto-updated Aug 5, 2026Security Bulletin: Langflow OSS is affected by arbitrary code execution in custom component validation and trusted code enforcement
https://www.ibm.com/support/pages/node/7282647Vendor Advisories for CVE-2026-9130(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 28× in last 7d / 70× 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-21 01:32 UTCEG score recompute
- 2026-08-21 01:32 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 12:36 UTCGHSA enrichment
- 2026-08-19 23:39 UTCEG score recompute
- 2026-08-19 23:39 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 10:43 UTCGHSA enrichment
- 2026-08-18 21:42 UTCEG score recompute
- 2026-08-18 21:42 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 08:39 UTCGHSA enrichment
- 2026-08-17 19:30 UTCEG score recompute
- 2026-08-17 19:30 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 06:16 UTCGHSA enrichment
- 2026-08-16 17:20 UTCEG score recompute
- 2026-08-16 17:20 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 04:24 UTCEG score recompute
- 2026-08-16 04:24 UTCGHSA enrichment
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 15:28 UTCGHSA enrichment
- 2026-08-15 02:31 UTCEG score recompute
Show 45 moreShow fewer
- 2026-08-15 02:31 UTCGHSA enrichment
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 13:35 UTCGHSA enrichment
- 2026-08-14 00:39 UTCEG score recompute
- 2026-08-14 00:39 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 11:43 UTCGHSA enrichment
- 2026-08-12 22:46 UTCEG score recompute
- 2026-08-12 22:46 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 09:50 UTCGHSA enrichment
- 2026-08-11 20:54 UTCEG score recompute
- 2026-08-11 20:54 UTCGHSA enrichment
- 2026-08-11 13:43 UTCEPSS rescore
- 2026-08-11 07:58 UTCEG score recompute
- 2026-08-11 07:58 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 19:02 UTCGHSA enrichment
- 2026-08-10 06:06 UTCGHSA enrichment
- 2026-08-09 17:10 UTCEG score recompute
- 2026-08-09 17:10 UTCGHSA enrichment
- 2026-08-09 13:47 UTCEPSS rescore
- 2026-08-09 04:14 UTCEG score recompute
- 2026-08-09 04:14 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 15:18 UTCGHSA enrichment
- 2026-08-08 02:21 UTCEG score recompute
- 2026-08-08 02:21 UTCGHSA enrichment
- 2026-08-07 16:30 UTCEPSS rescore
- 2026-08-07 13:25 UTCEG score recompute
- 2026-08-07 13:25 UTCGHSA enrichment
- 2026-08-07 13:13 UTCEG score recompute
- 2026-08-07 13:13 UTCGHSA enrichment
- 2026-08-07 07:51 UTCGHSA enrichment
- 2026-08-06 18:55 UTCGHSA enrichment
- 2026-08-06 15:48 UTCEG score recompute
- 2026-08-06 15:48 UTCGHSA enrichment
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 09:28 UTCEG score recompute
- 2026-08-06 09:28 UTCGHSA enrichment
- 2026-08-05 20:32 UTCEG score recompute
- 2026-08-05 20:15 UTCEG score recompute
- 2026-08-05 19:30 UTCEG score recompute
- 2026-08-05 18:26 UTCEG score recompute
- 2026-08-05 18:25 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-9130?
When was CVE-2026-9130 disclosed?
Is CVE-2026-9130 actively exploited?
What is the CVSS score of CVE-2026-9130?
How do I remediate CVE-2026-9130?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-9130
Is Your Infrastructure Affected by CVE-2026-9130?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.