CVE-2026-105697

CRITICALPre-NVD 9.99.9
EchelonGraph scoreHIGH confidence

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

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-07. A secondary CVSS source baseline 9.9; 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 week

Also known asEUVD-2026-92788 (ENISA EUVD) · GHSA-w794-rj3p-xv45 (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 9.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Langflow is a tool for building and deploying AI-powered agents and workflows. Before Langflow 1.10.3, the MCP stdio transport launched whatever command / args a user put in an MCP server configuration, with no allowlist and (before 1.10.3) wrapped in bash -c "exec {command} ...". Any user able to reach the MCP server settings ("Settings → MCP Servers → Add MCP Server", POST/PATCH /api/v2/mcp/servers/{server_name}) or to build a flow with the MCP Tools component could add a "server" whose command is an arbitrary OS command (touch, rm -rf, a reverse shell, ...). The command runs on the Langflow host as the Langflow process user as soon as Langflow tries to connect to the server (listing servers, loading tools, running the flow) — even when the UI then reports that the stdio server failed to start. With the default LANGFLOW_AUTO_LOGIN=true, GET /api/v1/auto_login hands out a token without credentials, so on an exposed instance running the default configuration this is reachable without an account. AUTO_LOGIN is documented as a development-only setting; with it disabled, any authenticated (non-admin) user can exploit it. This issue is fixed in Langflow 1.10.3, langflow-base 0.10.3, and lfx 1.10.3.

CVSS v3
9.9
EG Score
9.9CRITICALhigh confidence
EG Risk
45
EG Risk 45/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.9% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.9%
EPSS %ILE
61st
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.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.9% 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 or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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 or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

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

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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 5, 2026

Last Modified

October 9, 2026

Advisory Details (9)

Auto-updated Nov 2, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

Langflow < 1.10.3: OS command injection (RCE) via arbitrary command in MCP stdio server configuration · Advisory · langflow-ai/langflow · GitHub

https://github.com/langflow-ai/langflow/security/advisories/GHSA-w794-rj3p-xv45
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Authenticated RCE via MCP Stdio transport allows any user to execute arbitrary OS commands on the server · Advisory · langflow-ai/langflow · GitHub

https://github.com/langflow-ai/langflow/security/advisories/GHSA-7w94-79vh-5mr2
GitHub release Patch Available

1.10.3

Patch available: langflow-ai/langflow v1.10.3

https://github.com/langflow-ai/langflow/releases/tag/v1.10.3
GitHub pull request

fix(security): harden MCP stdio configuration

Fix merged in langflow-ai/langflow PR #14036 on 2026-07-14 — awaiting tagged release

https://github.com/langflow-ai/langflow/pull/14036
GitHub pull request

fix: prevent MCP command injection via allowlist validation (CWE-78)

Fix merged in langflow-ai/langflow PR #12290 on 2026-03-27 — awaiting tagged release

https://github.com/langflow-ai/langflow/pull/12290
GitHub commit

commit efbc4a16e639 (langflow-ai/langflow)

Fix landed in langflow-ai/langflow commit efbc4a16e639 — awaiting tagged release

https://github.com/langflow-ai/langflow/commit/efbc4a16e639409d938a4883463d27ef0bc637a0
GitHub commit

commit eba285edf1dd (langflow-ai/langflow)

Fix landed in langflow-ai/langflow commit eba285edf1dd — awaiting tagged release

https://github.com/langflow-ai/langflow/commit/eba285edf1dd4a33bf23a9cb8113c991fcdf3d1d
Web page

The Architectural Flaw at the Core of Anthropic's MCP

https://www.ox.security/blog/the-mother-of-all-ai-supply-chains-critical-systemic-vulnerability-at-the-core-of-the-mcp
Web page

MCP STDIO Command Injection: Full Vulnerability Advisory

https://www.ox.security/blog/mcp-supply-chain-advisory-rce-vulnerabilities-across-the-ai-ecosystem

Vendor Advisories for CVE-2026-105697(1)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
piplangflow @ 1.10.3 (fixes >= 1.1.2, < 1.10.3)—ghsa
piplangflow-base @ 0.10.3 (fixes >= 0.1.2, < 0.10.3)—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

(3 across 1 ecosystem)
PyPI(3)
PackageVulnerable rangeFix by version rangeDependents
langflow1.1.2 ... 1.9.6rc0 (62 versions)
  • 1.1.2 up to 1.10.3: fixed in 1.10.3
—
langflow-base0.1.2 ... 0.9.6rc0 (62 versions)
  • 0.1.2 up to 0.10.3: fixed in 0.10.3
—
lfx0.1.0 ... 1.10.3rc0 (46 versions)
  • every version up to 1.10.3: fixed in 1.10.3
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 65× 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-02 04:16 UTCEG score recompute
  2. 2026-11-02 04:16 UTCGHSA enrichmentGHSA-w794-rj3p-xv45 · GitHub severity CRITICAL · GitHub CVSS 9.9
  3. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.9% · 61st percentile
  4. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-w794-rj3p-xv45 · GitHub severity CRITICAL · GitHub CVSS 9.9
  5. 2026-11-01 08:00 UTCEG score recompute
  6. 2026-11-01 04:55 UTCEG score recompute
  7. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.9% · 61st percentile
  8. 2026-10-31 05:39 UTCEG score recompute
  9. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.9% · 61st percentile
  10. 2026-10-30 06:23 UTCEG score recompute
  11. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  12. 2026-10-29 07:07 UTCEG score recompute
  13. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  14. 2026-10-28 07:51 UTCEG score recompute
  15. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  16. 2026-10-27 08:35 UTCEG score recompute
  17. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  18. 2026-10-26 07:16 UTCEG score recompute
  19. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  20. 2026-10-25 14:55 UTCEG score recompute
  21. 2026-10-25 07:58 UTCEG score recompute
  22. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  23. 2026-10-24 08:42 UTCEG score recompute
  24. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  25. 2026-10-23 09:26 UTCEG score recompute
Show 40 more
  1. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  2. 2026-10-22 10:09 UTCEG score recompute
  3. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  4. 2026-10-21 10:48 UTCEG score recompute
  5. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  6. 2026-10-20 11:32 UTCEG score recompute
  7. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-10-19 12:13 UTCEG score recompute
  9. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  10. 2026-10-18 05:08 UTCEG score recompute
  11. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  12. 2026-10-17 07:24 UTCEG score recompute
  13. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  14. 2026-10-16 08:05 UTCEG score recompute
  15. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  16. 2026-10-15 07:08 UTCEG score recompute
  17. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  18. 2026-10-14 03:00 UTCEG score recompute
  19. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  20. 2026-10-12 16:39 UTCEG score recompute
  21. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  22. 2026-10-11 20:15 UTCEG score recompute
  23. 2026-10-11 18:27 UTCEG score recompute
  24. 2026-10-11 14:41 UTCEG score recompute
  25. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  26. 2026-10-10 23:20 UTCEG score recompute
  27. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  28. 2026-10-09 20:38 UTCEG score recompute
  29. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  30. 2026-10-09 20:05 UTCEG score recompute
  31. 2026-10-08 19:40 UTCEG score recompute
  32. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  33. 2026-10-08 01:41 UTCEG score recompute
  34. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  35. 2026-10-06 15:23 UTCEG score recompute
  36. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  37. 2026-10-06 14:55 UTCEG score recompute
  38. 2026-10-05 21:23 UTCEG score recompute
  39. 2026-10-05 21:09 UTCEG score recomputeFirst assessed: 9.9 CRITICAL
  40. 2026-10-05 21:05 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-105697?
CVE-2026-105697 is a critical-severity vulnerability; its CVE record was published on October 5, 2026. Langflow is a tool for building and deploying AI-powered agents and workflows. Before Langflow 1.10.3, the MCP stdio transport launched whatever command / args a user put in an MCP server configuration, with no allowlist and (before 1.10.3) wrapped in bash -c "exec {command} ...". Any user able to…
When was the CVE record for CVE-2026-105697 published?
The CVE record for CVE-2026-105697 was published on October 5, 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 9, 2026; the record at its source may have been updated since.
Is CVE-2026-105697 actively exploited?
CVE-2026-105697 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (61st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-105697?
CVE-2026-105697 has a CVSS base score of 9.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-105697?
A fix for CVE-2026-105697 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-105697 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-105697

Explore →

Is Your Infrastructure Affected by CVE-2026-105697?

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

Book a Demo →Browse All CVEs