CVE-2026-105789

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (53rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-93406 (ENISA EUVD)Source: ENISA EUVD

5.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 5.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Microsoft UFO is an open-source framework for intelligent automation across devices and platforms. Prior to 3.0.9, the execute_command tool in ufo/client/mcp/http_servers/linux_mcp_server.py treats sort and uniq as read-only commands while the free-form command parameter can select their file-output forms. An authenticated caller can use sort -o or the optional second uniq operand to create or overwrite files writable by the UFO server process without shell metacharacters, because the allowed binary opens the destination itself and the argument policy does not reject the operation. This can corrupt configuration or other writable data and disrupt the service, but the demonstrated primitive does not directly disclose files or establish arbitrary code execution. This issue is fixed in version 3.0.9.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
53rd
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 (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.

EG Severity
5.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 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 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

October 6, 2026

Last Modified

October 6, 2026

Advisory Details (4)

Auto-updated Oct 6, 2026
Patch available. Sources: github_pr, github_commit, github_release, github.
GitHub release Patch Available

Fixed security issues.

Patch available: microsoft/UFO v3.0.9

https://github.com/microsoft/UFO/releases/tag/v3.0.9
GitHub commit Patch Available

commit 4f793622794f (microsoft/UFO)

Patch available: microsoft/UFO v3.0.9 (contains commit 4f793622794f)

https://github.com/microsoft/UFO/commit/4f793622794f5d47810d54bed431c61f6a781dd6
GitHub pull request Patch Available

fix MSRC139482: UFO - ufo/client/mcp/http_servers/linux_mcp_server.py…

Patch available: microsoft/UFO v3.0.9 (PR #349 merged 2026-09-02)

https://github.com/microsoft/UFO/pull/349
GitHub advisoryMentions a patch (unverified)

Arbitrary file write in the Linux MCP `execute_command` tool · Advisory · microsoft/UFO · GitHub

https://github.com/microsoft/UFO/security/advisories/GHSA-85w2-wggf-rw49

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 43× 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:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  2. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  3. 2026-10-31 11:55 UTCOSV refresh
  4. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  5. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  6. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  7. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  8. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  9. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  10. 2026-10-25 14:55 UTCEG score recompute
  11. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  12. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  13. 2026-10-23 09:13 UTCEG score recompute
  14. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  15. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  16. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  17. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  18. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  19. 2026-10-18 05:08 UTCEG score recompute
  20. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  21. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  22. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  23. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  24. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  25. 2026-10-12 16:39 UTCEG score recompute
Show 18 more
  1. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  2. 2026-10-11 20:15 UTCEG score recompute
  3. 2026-10-11 18:27 UTCEG score recompute
  4. 2026-10-11 15:01 UTCEG score recompute
  5. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  6. 2026-10-11 13:31 UTCEG score recompute
  7. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  8. 2026-10-10 14:16 UTCEG score recompute
  9. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  10. 2026-10-09 15:03 UTCEG score recompute
  11. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  12. 2026-10-08 15:17 UTCEG score recompute
  13. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  14. 2026-10-06 15:27 UTCEG score recompute
  15. 2026-10-06 14:55 UTCEG score recompute
  16. 2026-10-06 14:30 UTCEG score recompute
  17. 2026-10-06 14:10 UTCEG score recomputeFirst assessed: 5.4 MEDIUM
  18. 2026-10-06 14:09 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-105789?
CVE-2026-105789 is a medium-severity vulnerability; its CVE record was published on October 6, 2026. Microsoft UFO is an open-source framework for intelligent automation across devices and platforms. Prior to 3.0.9, the execute_command tool in ufo/client/mcp/http_servers/linux_mcp_server.py treats sort and uniq as read-only commands while the free-form command parameter can select their…
When was the CVE record for CVE-2026-105789 published?
The CVE record for CVE-2026-105789 was published on October 6, 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-105789 actively exploited?
CVE-2026-105789 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-105789?
CVE-2026-105789 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-105789?
A fix for CVE-2026-105789 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-105789?

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