CVE-2026-7755

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-17. A secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
8.8EG
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.7%CVSS: 8.8Exploit: None knownExposed services: Not assessed

IBM strongly recommends addressing the vulnerability now by upgrading Langflow OSS to version 1.10.1 https://pypi.org/project/langflow/ (from the CVE record's solution, IBM Corporation) — apply it.

IBM Langflow OSS 1.0.0 through 1.10.0 Langflow could allow remote code execution due to incomplete validation enforcement on MCP server configuration files.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.8% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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 strongly recommends addressing the vulnerability now by upgrading Langflow OSS to version 1.10.1 https://pypi.org/project/langflow/ (from the CVE record's solution, IBM Corporation). Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
53rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

IBM strongly recommends addressing the vulnerability now by upgrading Langflow OSS to version 1.10.1 https://pypi.org/project/langflow/ (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 total (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)14 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 total (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

July 17, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jul 17, 2026
Fix named in the CVE record's solution (IBM Corporation).
Web page

Security Bulletin: MCP Server Configuration Validator Bypass via File Upload API

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

Vendor Advisories for CVE-2026-7755(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 13× in last 7d / 46× 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 96 of 229 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 133 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-7755?
CVE-2026-7755 is a high-severity vulnerability; its CVE record was published on July 17, 2026. IBM Langflow OSS 1.0.0 through 1.10.0 Langflow could allow remote code execution due to incomplete validation enforcement on MCP server configuration files.
When was the CVE record for CVE-2026-7755 published?
The CVE record for CVE-2026-7755 was published on July 17, 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 July 23, 2026; the record at its source may have been updated since.
Is CVE-2026-7755 actively exploited?
CVE-2026-7755 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-7755?
CVE-2026-7755 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-7755?
The CVE record's solution for CVE-2026-7755, written by its CNA IBM Corporation, names the fix: "IBM strongly recommends addressing the vulnerability now by upgrading Langflow OSS to version 1.10.1 https://pypi.org/project/langflow/". The vendor advisories EchelonGraph has for CVE-2026-7755 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-7755?

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

Book a Demo →Browse All CVEs