CVE-2026-9130

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM 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 fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.1Exploit: None knownExposed services: Not assessed

IBM recommends upgrading to Langflow OSS 1.11.0 or newer https://github.com/langflow-ai/langflow/releases (from the CVE record's solution, IBM Corporation) — apply it.

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.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

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 (value × EchelonGraph’s weight)
Severity71% × 45%
The EG Score, 7.1 of 10.
Exploitation0% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: IBM recommends upgrading to Langflow OSS 1.11.0 or newer https://github.com/langflow-ai/langflow/releases (from the CVE record's solution, IBM Corporation). Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

IBM recommends upgrading to Langflow OSS 1.11.0 or newer https://github.com/langflow-ai/langflow/releases (from the CVE record's solution, IBM Corporation). Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 5, 2026

Last Modified

August 7, 2026

Advisory Details (1)

Auto-updated Aug 5, 2026
Fix named in the CVE record's solution (IBM Corporation).
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 17× in last 7d / 85× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 226 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 127 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 19:13 UTCEG score recompute
  2. 2026-10-11 16:30 UTCEG score recompute
  3. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  4. 2026-10-11 13:44 UTCEG score recompute
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  6. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  7. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  8. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  9. 2026-10-06 23:36 UTCEG score recompute
  10. 2026-10-06 23:36 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  11. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  12. 2026-10-05 19:33 UTCEG score recompute
  13. 2026-10-05 19:32 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  14. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  15. 2026-10-04 23:30 UTCEG score recompute
  16. 2026-10-04 23:30 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  17. 2026-10-04 23:23 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  18. 2026-10-04 05:58 UTCEG score recompute
  19. 2026-10-04 05:58 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  20. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  21. 2026-10-03 01:07 UTCEG score recompute
  22. 2026-10-03 01:07 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  23. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  24. 2026-10-02 09:51 UTCEG score recompute
  25. 2026-10-02 09:51 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
Show 74 more
  1. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-10-01 15:11 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  3. 2026-10-01 02:15 UTCEG score recompute
  4. 2026-10-01 02:15 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  5. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  6. 2026-09-29 06:13 UTCEG score recompute
  7. 2026-09-29 06:13 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  8. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  9. 2026-09-28 06:35 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  10. 2026-09-27 17:39 UTCEG score recompute
  11. 2026-09-27 17:39 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  12. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  13. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  14. 2026-09-25 04:30 UTCEG score recompute
  15. 2026-09-25 04:30 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  16. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  17. 2026-09-24 10:16 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  18. 2026-09-23 21:20 UTCEG score recompute
  19. 2026-09-23 21:20 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  20. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  21. 2026-09-23 04:09 UTCEG score recompute
  22. 2026-09-23 04:09 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  23. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  24. 2026-09-22 15:08 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  25. 2026-09-22 02:12 UTCEG score recompute
  26. 2026-09-22 02:11 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  27. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  28. 2026-09-21 13:12 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  29. 2026-09-20 20:47 UTCEG score recompute
  30. 2026-09-20 20:47 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  31. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  32. 2026-09-19 23:14 UTCEG score recompute
  33. 2026-09-19 23:14 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  34. 2026-09-19 07:39 UTCEG score recompute
  35. 2026-09-19 07:39 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  36. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  37. 2026-09-18 17:45 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  38. 2026-09-18 04:48 UTCEG score recompute
  39. 2026-09-18 04:48 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  40. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  41. 2026-09-17 15:52 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  42. 2026-09-17 01:05 UTCEG score recompute
  43. 2026-09-17 01:05 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  44. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  45. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  46. 2026-09-16 05:13 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  47. 2026-09-15 16:14 UTCEG score recompute
  48. 2026-09-15 16:14 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  49. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  50. 2026-09-15 01:22 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  51. 2026-09-14 07:21 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  52. 2026-09-13 18:25 UTCEG score recompute
  53. 2026-09-13 18:25 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  54. 2026-09-13 16:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  55. 2026-09-13 05:28 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  56. 2026-09-12 16:32 UTCEG score recompute
  57. 2026-09-12 16:32 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  58. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  59. 2026-09-12 03:36 UTCEG score recompute
  60. 2026-09-12 03:36 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  61. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  62. 2026-09-11 14:39 UTCEG score recompute
  63. 2026-09-11 14:39 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  64. 2026-09-11 09:38 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  65. 2026-09-10 21:09 UTCEG score recompute
  66. 2026-09-10 21:09 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  67. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  68. 2026-09-10 08:12 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  69. 2026-09-09 19:16 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  70. 2026-09-09 06:19 UTCEG score recompute
  71. 2026-09-09 06:19 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  72. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  73. 2026-09-08 07:58 UTCGHSA enrichmentGHSA-vph6-jp7f-x3cx · GitHub severity HIGH · GitHub CVSS 7.1
  74. 2026-09-07 18:12 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-9130?
CVE-2026-9130 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-9130 published?
The CVE record for CVE-2026-9130 was published on August 5, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 7, 2026; the record at its source may have been updated since.
Is CVE-2026-9130 actively exploited?
CVE-2026-9130 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-9130?
CVE-2026-9130 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-9130?
The CVE record's solution for CVE-2026-9130, written by its CNA IBM Corporation, names the fix: "IBM recommends upgrading to Langflow OSS 1.11.0 or newer https://github.com/langflow-ai/langflow/releases" The vendor advisories EchelonGraph has for CVE-2026-9130 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs