CVE-2026-19286

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-29. A secondary CVSS source baseline 9.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 weekElevated
9.8EG
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).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 9.8Exploit: Public PoCExposed services: Not assessed

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

IBM Langflow OSS 1.0.0 through 1.11.1 could allow a remote attacker to execute arbitrary code due to improper enforcement of security restrictions on the A2A public endpoint.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/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)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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: IBM strongly recommends addressing the vulnerability now by upgrading Langflow OSS to version 1.11.2 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.8%
EPSS %ILE
55th
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.11.2 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 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

August 28, 2026

Last Modified

September 1, 2026

Advisory Details (1)

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

Security Bulletin: Langflow is affected by multiple remote code execution vulnerabilities due to insufficient code-execution policy enforcement

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

Vendor Advisories for CVE-2026-19286(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 29× in last 7d / 200× 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 346 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 246 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.8% · 55th percentile
  2. 2026-10-14 09:58 UTCEG score recompute
  3. 2026-10-14 09:58 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  5. 2026-10-13 08:02 UTCEG score recompute
  6. 2026-10-13 08:02 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  8. 2026-10-12 16:26 UTCEG score recompute
  9. 2026-10-12 09:25 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-11 20:06 UTCEG score recompute
  11. 2026-10-11 17:19 UTCEG score recompute
  12. 2026-10-11 14:51 UTCEG score recompute
  13. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  14. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  15. 2026-10-10 13:14 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-10 09:36 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-10 05:15 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-10 00:47 UTCEG score recompute
  19. 2026-10-10 00:47 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  21. 2026-10-09 06:14 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-09 02:36 UTCEG score recompute
  23. 2026-10-09 02:36 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  25. 2026-10-08 08:11 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 75 more
  1. 2026-10-08 04:33 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-10-08 00:48 UTCEG score recompute
  3. 2026-10-08 00:47 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  5. 2026-10-07 09:25 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-07 05:47 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-07 02:10 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-06 22:04 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-06 18:26 UTCEG score recompute
  10. 2026-10-06 18:26 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  12. 2026-10-06 14:49 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-06 11:09 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-06 07:27 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-06 00:47 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-05 20:29 UTCEG score recompute
  17. 2026-10-05 20:29 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  19. 2026-10-05 16:49 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-05 11:18 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-05 07:17 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-05 03:39 UTCEG score recompute
  23. 2026-10-05 03:39 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  25. 2026-10-04 23:12 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-10-04 19:35 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-10-04 15:44 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-10-04 12:06 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-10-04 08:29 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  30. 2026-10-04 04:51 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-10-04 01:13 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-03 20:52 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  33. 2026-10-03 17:15 UTCEG score recompute
  34. 2026-10-03 17:15 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  35. 2026-10-03 13:38 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-10-03 04:11 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-10-03 00:34 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  38. 2026-10-02 20:56 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-10-02 17:08 UTCEG score recompute
  40. 2026-10-02 17:08 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-10-02 13:31 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-10-02 09:51 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-02 06:14 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-10-02 00:36 UTCEG score recompute
  45. 2026-10-02 00:36 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-10-01 19:54 UTCEG score recompute
  47. 2026-10-01 19:54 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  49. 2026-10-01 16:17 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-10-01 12:40 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-10-01 09:03 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-10-01 05:26 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-10-01 00:59 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-09-30 19:48 UTCEG score recompute
  55. 2026-09-30 19:48 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  57. 2026-09-30 11:32 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-09-30 07:26 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-09-30 03:48 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-09-29 15:33 UTCEG score recompute
  61. 2026-09-29 15:33 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  63. 2026-09-29 11:56 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-09-29 08:17 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-09-29 04:30 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-09-29 00:52 UTCEG score recompute
  67. 2026-09-29 00:52 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-09-28 21:07 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-09-28 15:47 UTCEG score recompute
  70. 2026-09-28 15:47 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  72. 2026-09-28 12:05 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  73. 2026-09-28 08:28 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-09-28 04:51 UTCGHSA enrichmentGHSA-8ffw-jjx8-5788 · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-09-28 01:14 UTCEG score recompute

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCrmhowe425/POC-CVE-2026-19286
    Published Aug 29, 2026

    Proof of concept exploit code for CVE-2026-19286

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-19286?
CVE-2026-19286 is a critical-severity vulnerability; its CVE record was published on August 28, 2026. IBM Langflow OSS 1.0.0 through 1.11.1 could allow a remote attacker to execute arbitrary code due to improper enforcement of security restrictions on the A2A public endpoint.
When was the CVE record for CVE-2026-19286 published?
The CVE record for CVE-2026-19286 was published on August 28, 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 September 1, 2026; the record at its source may have been updated since.
Is CVE-2026-19286 actively exploited?
CVE-2026-19286 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-19286?
CVE-2026-19286 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-19286?
The CVE record's solution for CVE-2026-19286, written by its CNA IBM Corporation, names the fix: "IBM strongly recommends addressing the vulnerability now by upgrading Langflow OSS to version 1.11.2 https://pypi.org/project/langflow/". The vendor advisories EchelonGraph has for CVE-2026-19286 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-19286?

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

Book a Demo →Browse All CVEs