CVE-2026-17630

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: 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 could allow a remote attacker to execute arbitrary code due to improper validation of configuration parameters.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
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 is affected by security vulnerabilities in Model Context Protocol features

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

Vendor Advisories for CVE-2026-17630(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 27× in last 7d / 66× 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-20 08:56 UTCGHSA enrichment
  2. 2026-08-19 20:39 UTCEG score recompute
  3. 2026-08-19 20:39 UTCGHSA enrichment
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-19 08:22 UTCGHSA enrichment
  6. 2026-08-18 20:04 UTCEG score recompute
  7. 2026-08-18 20:04 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-18 07:47 UTCGHSA enrichment
  10. 2026-08-17 19:30 UTCEG score recompute
  11. 2026-08-17 19:30 UTCGHSA enrichment
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 06:46 UTCGHSA enrichment
  14. 2026-08-16 18:30 UTCEG score recompute
  15. 2026-08-16 18:30 UTCGHSA enrichment
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 06:13 UTCEG score recompute
  18. 2026-08-16 06:13 UTCGHSA enrichment
  19. 2026-08-16 02:14 UTCEPSS rescore
  20. 2026-08-15 17:56 UTCGHSA enrichment
  21. 2026-08-15 05:39 UTCEG score recompute
  22. 2026-08-15 05:39 UTCGHSA enrichment
  23. 2026-08-15 01:30 UTCEPSS rescore
  24. 2026-08-14 17:22 UTCGHSA enrichment
  25. 2026-08-14 05:05 UTCEG score recompute
Show 41 more
  1. 2026-08-14 05:05 UTCGHSA enrichment
  2. 2026-08-13 22:00 UTCEPSS rescore
  3. 2026-08-13 16:48 UTCGHSA enrichment
  4. 2026-08-13 04:31 UTCGHSA enrichment
  5. 2026-08-12 16:14 UTCEG score recompute
  6. 2026-08-12 16:14 UTCGHSA enrichment
  7. 2026-08-12 13:50 UTCEPSS rescore
  8. 2026-08-12 03:58 UTCGHSA enrichment
  9. 2026-08-11 15:40 UTCEG score recompute
  10. 2026-08-11 15:40 UTCGHSA enrichment
  11. 2026-08-11 13:42 UTCEPSS rescore
  12. 2026-08-11 03:23 UTCEG score recompute
  13. 2026-08-11 03:23 UTCGHSA enrichment
  14. 2026-08-11 00:00 UTCEPSS rescore
  15. 2026-08-10 15:07 UTCGHSA enrichment
  16. 2026-08-10 02:49 UTCGHSA enrichment
  17. 2026-08-09 14:32 UTCEG score recompute
  18. 2026-08-09 14:32 UTCGHSA enrichment
  19. 2026-08-09 13:46 UTCEPSS rescore
  20. 2026-08-09 02:16 UTCEG score recompute
  21. 2026-08-09 02:16 UTCGHSA enrichment
  22. 2026-08-08 16:37 UTCEPSS rescore
  23. 2026-08-08 13:59 UTCGHSA enrichment
  24. 2026-08-08 01:42 UTCEG score recompute
  25. 2026-08-08 01:42 UTCGHSA enrichment
  26. 2026-08-07 13:25 UTCGHSA enrichment
  27. 2026-08-07 13:13 UTCGHSA enrichment
  28. 2026-08-07 07:52 UTCGHSA enrichment
  29. 2026-08-06 19:35 UTCEG score recompute▲ 1.60
  30. 2026-08-06 19:35 UTCGHSA enrichment
  31. 2026-08-06 19:35 UTCNVD updateCVSS v3 → 8.8
  32. 2026-08-06 15:49 UTCEG score recompute
  33. 2026-08-06 15:49 UTCGHSA enrichment
  34. 2026-08-06 13:46 UTCEPSS rescore
  35. 2026-08-06 05:25 UTCEG score recompute
  36. 2026-08-06 05:25 UTCGHSA enrichment
  37. 2026-08-06 04:25 UTCEG score recompute
  38. 2026-08-06 04:25 UTCGHSA enrichment
  39. 2026-08-05 17:29 UTCEG score recompute
  40. 2026-08-05 16:51 UTCEG score recompute
  41. 2026-08-05 16:50 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-17630?
CVE-2026-17630 is a high vulnerability published on August 5, 2026. IBM Langflow OSS 1.0.0 through 1.10.3 could allow a remote attacker to execute arbitrary code due to improper validation of configuration parameters.
When was CVE-2026-17630 disclosed?
CVE-2026-17630 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-17630 actively exploited?
CVE-2026-17630 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 64.7% of all scored CVEs.
What is the CVSS score of CVE-2026-17630?
CVE-2026-17630 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-17630?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-17630, 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-17630

Explore →

Is Your Infrastructure Affected by CVE-2026-17630?

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

Start Free Scan →Browse All CVEs