CVE-2026-9130

HIGHPre-NVD 7.17.1
EchelonGraph scoreHIGH confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

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

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.

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 computed
Severity71% × 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, 2026
No patch confirmed yet.
generic

Security Bulletin: Langflow OSS is affected by arbitrary code execution in custom component validation and trusted code enforcement

https://www.ibm.com/support/pages/node/7282647

Vendor 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.

  1. 2026-08-21 01:32 UTCEG score recompute
  2. 2026-08-21 01:32 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 12:36 UTCGHSA enrichment
  5. 2026-08-19 23:39 UTCEG score recompute
  6. 2026-08-19 23:39 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 10:43 UTCGHSA enrichment
  9. 2026-08-18 21:42 UTCEG score recompute
  10. 2026-08-18 21:42 UTCGHSA enrichment
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 08:39 UTCGHSA enrichment
  13. 2026-08-17 19:30 UTCEG score recompute
  14. 2026-08-17 19:30 UTCGHSA enrichment
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 06:16 UTCGHSA enrichment
  17. 2026-08-16 17:20 UTCEG score recompute
  18. 2026-08-16 17:20 UTCGHSA enrichment
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 04:24 UTCEG score recompute
  22. 2026-08-16 04:24 UTCGHSA enrichment
  23. 2026-08-16 02:15 UTCEPSS rescore
  24. 2026-08-15 15:28 UTCGHSA enrichment
  25. 2026-08-15 02:31 UTCEG score recompute
Show 45 more
  1. 2026-08-15 02:31 UTCGHSA enrichment
  2. 2026-08-15 01:31 UTCEPSS rescore
  3. 2026-08-14 13:35 UTCGHSA enrichment
  4. 2026-08-14 00:39 UTCEG score recompute
  5. 2026-08-14 00:39 UTCGHSA enrichment
  6. 2026-08-13 22:00 UTCEPSS rescore
  7. 2026-08-13 11:43 UTCGHSA enrichment
  8. 2026-08-12 22:46 UTCEG score recompute
  9. 2026-08-12 22:46 UTCGHSA enrichment
  10. 2026-08-12 13:51 UTCEPSS rescore
  11. 2026-08-12 09:50 UTCGHSA enrichment
  12. 2026-08-11 20:54 UTCEG score recompute
  13. 2026-08-11 20:54 UTCGHSA enrichment
  14. 2026-08-11 13:43 UTCEPSS rescore
  15. 2026-08-11 07:58 UTCEG score recompute
  16. 2026-08-11 07:58 UTCGHSA enrichment
  17. 2026-08-11 00:00 UTCEPSS rescore
  18. 2026-08-10 19:02 UTCGHSA enrichment
  19. 2026-08-10 06:06 UTCGHSA enrichment
  20. 2026-08-09 17:10 UTCEG score recompute
  21. 2026-08-09 17:10 UTCGHSA enrichment
  22. 2026-08-09 13:47 UTCEPSS rescore
  23. 2026-08-09 04:14 UTCEG score recompute
  24. 2026-08-09 04:14 UTCGHSA enrichment
  25. 2026-08-08 16:37 UTCEPSS rescore
  26. 2026-08-08 15:18 UTCGHSA enrichment
  27. 2026-08-08 02:21 UTCEG score recompute
  28. 2026-08-08 02:21 UTCGHSA enrichment
  29. 2026-08-07 16:30 UTCEPSS rescore
  30. 2026-08-07 13:25 UTCEG score recompute
  31. 2026-08-07 13:25 UTCGHSA enrichment
  32. 2026-08-07 13:13 UTCEG score recompute
  33. 2026-08-07 13:13 UTCGHSA enrichment
  34. 2026-08-07 07:51 UTCGHSA enrichment
  35. 2026-08-06 18:55 UTCGHSA enrichment
  36. 2026-08-06 15:48 UTCEG score recompute
  37. 2026-08-06 15:48 UTCGHSA enrichment
  38. 2026-08-06 13:47 UTCEPSS rescore
  39. 2026-08-06 09:28 UTCEG score recompute
  40. 2026-08-06 09:28 UTCGHSA enrichment
  41. 2026-08-05 20:32 UTCEG score recompute
  42. 2026-08-05 20:15 UTCEG score recompute
  43. 2026-08-05 19:30 UTCEG score recompute
  44. 2026-08-05 18:26 UTCEG score recompute
  45. 2026-08-05 18:25 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-9130?
CVE-2026-9130 is a high vulnerability published on August 5, 2026. 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 sessionid collision. The MemoryComponent.retrievemessages and storemessage methods filter on sessionid without…
When was CVE-2026-9130 disclosed?
CVE-2026-9130 was first published in the National Vulnerability Database on August 5, 2026, with the most recent update on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9130 actively exploited?
CVE-2026-9130 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.7% of all scored CVEs.
What is the CVSS score of CVE-2026-9130?
CVE-2026-9130 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-9130?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9130, 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

Explore the affected products and dependency analysis for CVE-2026-9130

Explore →

Is Your Infrastructure Affected by CVE-2026-9130?

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