CVE-2026-10560

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.5% (40th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.2 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-06-30) is not newer than that change (2026-07-02), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.1Exploit: None knownExposed services: Not assessed

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

IBM Langflow OSS 1.0.0 through 1.9.6 contains a missing authentication vulnerability in /api/v1/build_public_tmp/ endpoints that allows an unauthenticated attacker to read build event data or cancel jobs using a valid job identifier, resulting in information disclosure and denial of service.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/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)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 strongly recommends addressing the vulnerability now by upgrading Langflow OSS to version 1.10.0 https://pypi.org/project/langflow/ (from the CVE record's solution, IBM Corporation). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

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

IBM strongly recommends addressing the vulnerability now by upgrading Langflow OSS to version 1.10.0 https://pypi.org/project/langflow/ (from the CVE record's solution, IBM Corporation). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

June 30, 2026

Last Modified

July 2, 2026

Advisory Details (1)

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

Security Bulletin: Unauthenticated Access to Private Flow Build Events and Cancellation in Langflow OSS

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

Vendor Advisories for CVE-2026-10560(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 16× in last 7d / 35× 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 100 of 350 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. None are among the latest 100 rows. The 250 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-10560?
CVE-2026-10560 is a critical-severity vulnerability; its CVE record was published on June 30, 2026. IBM Langflow OSS 1.0.0 through 1.9.6 contains a missing authentication vulnerability in /api/v1/buildpublictmp/ endpoints that allows an unauthenticated attacker to read build event data or cancel jobs using a valid job identifier, resulting in information disclosure and denial of service.
When was the CVE record for CVE-2026-10560 published?
The CVE record for CVE-2026-10560 was published on June 30, 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 2, 2026; the record at its source may have been updated since.
Is CVE-2026-10560 actively exploited?
CVE-2026-10560 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-10560?
CVE-2026-10560 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-10560?
The CVE record's solution for CVE-2026-10560, written by its CNA IBM Corporation, names the fix: "IBM strongly recommends addressing the vulnerability now by upgrading Langflow OSS to version 1.10.0 https://pypi.org/project/langflow/". The vendor advisories EchelonGraph has for CVE-2026-10560 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-10560?

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

Book a Demo →Browse All CVEs