CVE-2026-51886

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.6% (48th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.8 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-10-05) is not newer than that change (2026-10-06), so it does not.

Triggered by: Headline CVSS from CISA-ADP (Vulnrichment) CVSS v3.1
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-91120 (ENISA EUVD) · GHSA-qqw9-2vj9-hx7r (GitHub Security Advisories) · GHSA-w584-2h2r-2hvf (GitHub Security Advisories)Source: ENISA EUVD

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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

langflow-ai langflow v1.9.3 is affected by: Code Injection. The impact is: execute arbitrary code (remote). The component is: src/backend/base/langflow/api/v1/validate.py:validate-post_validate_code-a-real-authenticated-http-post-to-api-v1. The attack vector is: Attack surface: HTTP or browser-backed service path. A public-facing route accepts raw Python source and forwards it into a server-side compile/exec validation path without any visible entitlement guard. ¶¶ A weakness has been identified in langflow-ai langflow up to 1.9.3. langflow contains a code injection vulnerability in validate-post_validate_code-a-real-authenticated-http-post-to-api-v1 (src/backend/base/langflow/api/v1/validate.py:13). An authenticated attacker can execute arbitrary Python code on the server by submitting malicious code to the /api/v1/validate/code endpoint, which directly executes user-supplied code without sandboxing or security controls.

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 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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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.6%
EPSS %ILE
48th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.CISA-ADP (Vulnrichment) CVSS v3.1 · CVSS v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (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.

The score's inputs: 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

October 1, 2026

Last Modified

October 6, 2026

Advisory Details (2)

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

Code Injection in `/api/v1/validate/code` Endpoint · Issue #13336 · langflow-ai/langflow · GitHub

https://github.com/langflow-ai/langflow/issues/13336
Web page

CVE-2026-51886 - Code Injection in langflow (validate.py:post_validate_code) · GitHub

https://gist.github.com/Ro1ME/c11b1e63e4e8fca6b25275144f25ec2a

Vendor Advisories for CVE-2026-51886(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
piplangflow @ 1.10.1 (fixes >= 1.7.2, < 1.10.1)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
langflow1.10.0 ... 1.9.6rc0 (28 versions)
  • 1.7.2 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 16× in last 7d / 66× 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.

  1. 2026-11-01 16:51 UTCEG score recompute
  2. 2026-11-01 16:50 UTCGHSA enrichmentGHSA-w584-2h2r-2hvf · GitHub severity HIGH · GitHub CVSS 8.8
  3. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  4. 2026-11-01 07:45 UTCGHSA enrichmentGHSA-w584-2h2r-2hvf · GitHub severity HIGH · GitHub CVSS 8.8
  5. 2026-11-01 07:45 UTCEG score recompute
  6. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  7. 2026-10-31 14:57 UTCEG score recompute
  8. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  9. 2026-10-30 13:04 UTCEG score recompute
  10. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  11. 2026-10-29 11:10 UTCEG score recompute
  12. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  13. 2026-10-28 09:12 UTCEG score recompute
  14. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  15. 2026-10-27 06:45 UTCEG score recompute
  16. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  17. 2026-10-26 01:22 UTCEG score recompute
  18. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  19. 2026-10-25 14:21 UTCEG score recompute
  20. 2026-10-24 23:29 UTCEG score recompute
  21. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  22. 2026-10-23 21:36 UTCEG score recompute
  23. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  24. 2026-10-22 19:36 UTCEG score recompute
  25. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
Show 47 more
  1. 2026-10-21 17:43 UTCEG score recompute
  2. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-10-20 15:50 UTCEG score recompute
  5. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-10-19 13:55 UTCEG score recompute
  7. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-10-18 03:32 UTCEG score recompute
  9. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-10-17 10:08 UTCEG score recompute
  11. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  12. 2026-10-16 08:14 UTCEG score recompute
  13. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  14. 2026-10-15 06:20 UTCEG score recompute
  15. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  16. 2026-10-14 02:01 UTCEG score recompute
  17. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  18. 2026-10-12 22:18 UTCEG score recompute
  19. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  20. 2026-10-12 15:58 UTCEG score recompute
  21. 2026-10-11 19:41 UTCEG score recompute
  22. 2026-10-11 16:56 UTCEG score recompute
  23. 2026-10-11 14:20 UTCEG score recompute
  24. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  25. 2026-10-10 21:47 UTCEG score recompute
  26. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  27. 2026-10-09 20:56 UTCEG score recompute
  28. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  29. 2026-10-08 20:06 UTCEG score recompute
  30. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  31. 2026-10-08 03:18 UTCEG score recompute
  32. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  33. 2026-10-06 18:17 UTCEG score recompute
  34. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  35. 2026-10-06 01:33 UTCEG score recompute
  36. 2026-10-06 00:41 UTCEG score recomputeFirst assessed: 9.8 CRITICAL
  37. 2026-10-06 00:40 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  38. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  39. 2026-10-05 11:48 UTCGHSA enrichmentGHSA-qqw9-2vj9-hx7r
  40. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  41. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  42. 2026-10-02 18:16 UTCEG score recompute
  43. 2026-10-02 18:16 UTCGHSA enrichmentGHSA-qqw9-2vj9-hx7r
  44. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  45. 2026-10-01 22:17 UTCNVD update
  46. 2026-10-01 21:48 UTCEG score recompute
  47. 2026-10-01 21:45 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-51886?
CVE-2026-51886 is a critical-severity vulnerability; its CVE record was published on October 1, 2026. langflow-ai langflow v1.9.3 is affected by: Code Injection. The impact is: execute arbitrary code (remote). The component is: src/backend/base/langflow/api/v1/validate.py:validate-post_validate_code-a-real-authenticated-http-post-to-api-v1. The attack vector is: Attack surface: HTTP or…
When was the CVE record for CVE-2026-51886 published?
The CVE record for CVE-2026-51886 was published on October 1, 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 October 6, 2026; the record at its source may have been updated since.
Is CVE-2026-51886 actively exploited?
CVE-2026-51886 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-51886?
CVE-2026-51886 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-51886?
A fix for CVE-2026-51886 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-51886 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-51886

Explore →

Is Your Infrastructure Affected by CVE-2026-51886?

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

Book a Demo →Browse All CVEs