CVE-2026-10561

CRITICALPre-NVD 10.010.0
EchelonGraph scoreMEDIUM confidence

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

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-22. A secondary CVSS source baseline 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
10.0EG
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.8%CVSS: 10.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (IBM Corporation) states them: "IBM strongly recommends addressing the vulnerability now by upgrading Langflow OSS to version 1.9.4 https://pypi.org/project/langflow/".

IBM Langflow OSS 1.0.0 through 1.9.3 has an vulnerability due to an improper isolation of Python execution combined with an authentication bypass that allows an unauthenticated attacker to execute arbitrary code on the host system, resulting in complete compromise

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
60
EG Risk 60/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.8% × 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 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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
56th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-20). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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

A fix is available. 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 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)3 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 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

June 22, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Oct 17, 2026
Patch available.
Web page

Security Bulletin: Unauthenticated Remote Code Execution in Langflow OSS PythonREPLComponent via Builtins Injection

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

Vendor Advisories for CVE-2026-10561(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
langflow0.0.31 ... 1.9.6rc0 (306 versions)
  • every version up to 1.10.1: fixed in 1.10.1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 38× 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 468 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 368 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-10561?
CVE-2026-10561 is a critical-severity vulnerability; its CVE record was published on June 22, 2026. IBM Langflow OSS 1.0.0 through 1.9.3 has an vulnerability due to an improper isolation of Python execution combined with an authentication bypass that allows an unauthenticated attacker to execute arbitrary code on the host system, resulting in complete compromise
When was the CVE record for CVE-2026-10561 published?
The CVE record for CVE-2026-10561 was published on June 22, 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 June 26, 2026; the record at its source may have been updated since.
Is CVE-2026-10561 actively exploited?
CVE-2026-10561 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (56th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-10561?
CVE-2026-10561 has a CVSS base score of 10.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-10561?
A fix for CVE-2026-10561 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (IBM Corporation) states them: "IBM strongly recommends addressing the vulnerability now by upgrading Langflow OSS to version 1.9.4 https://pypi.org/project/langflow/". The vendor advisories EchelonGraph has for CVE-2026-10561 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-10561

Explore →

Is Your Infrastructure Affected by CVE-2026-10561?

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