CVE-2026-81735

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-08-27. The CNA's CVSS baseline 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
10.0EG
EchelonGraph verdictPlan mitigationRemediate 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

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

startServer.ts in the mcp-http-server package of UI-TARS-desktop defaulted its listen address to '::' when no host was given, so startSseAndStreamableHttpMcpServer bound the Streamable HTTP and SSE MCP transports to every interface, and its authentication middleware was optional: middlewares are applied only when a caller supplies them. The @agent-infra/mcp-server-commands and @agent-infra/mcp-server-filesystem entry points call startSseAndStreamableHttpMcpServer with a host and port alone and pass no middleware, so neither server required a credential. The commands server exposes a run_command tool that hands its caller-supplied command string to promisify(child_process.exec), so any unauthenticated client able to reach the port could run arbitrary commands as the user running the server, and the filesystem server exposed its file read and write tools on the same terms. The listen default became 127.0.0.1 in commit c2ad42e3eb9b27830db41a3e6f51ca7179d9b168; the package version stayed at 1.2.4 across that change, so the boundary is the commit rather than a release.

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 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)
Severity100% × 45%
The EG Score, 10.0 of 10.
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: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.
EPSS PROB
0.8%
EPSS %ILE
54th
KEV
Not listed

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

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.

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 27, 2026

Last Modified

September 24, 2026

Advisory Details (5)

Auto-updated Oct 8, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr, github_commit.
Web page

UI-TARS-desktop @agent-infra MCP Servers Bind Every Interface Without Authentication, Exposing Arbitrary Command Execution | Advisories | VulnCheck

https://www.vulncheck.com/advisories/ui-tars-desktop-agent-infra-mcp-servers-bind-every-interface-without-authentication-exposing-arbitrary-command-execution
Web page

UI-TARS-desktop/packages/agent-infra/mcp-http-server/src/startServer.ts at e9f3387288da4af2ad99972da2ac916cdabce093 · bytedance/UI-TARS-desktop · GitHub

https://github.com/bytedance/UI-TARS-desktop/blob/e9f3387288da4af2ad99972da2ac916cdabce093/packages/agent-infra/mcp-http-server/src/startServer.ts#L263
Web page

GitHub - bytedance/UI-TARS-desktop: The Open-Source Multimodal AI Agent Stack: Connecting Cutting-Edge AI Models and Agent Infra · GitHub

https://github.com/bytedance/UI-TARS-desktop
GitHub commit

commit c2ad42e3eb9b (bytedance/UI-TARS-desktop)

Fix landed in bytedance/UI-TARS-desktop commit c2ad42e3eb9b — awaiting tagged release

https://github.com/bytedance/UI-TARS-desktop/commit/c2ad42e3eb9b27830db41a3e6f51ca7179d9b168
GitHub pull request

fix(mcp-http-server): default host to 127.0.0.1, not all interfaces

Fix merged in bytedance/UI-TARS-desktop PR #1918 on 2026-07-01 — awaiting tagged release

https://github.com/bytedance/UI-TARS-desktop/pull/1918

Vendor Advisories for CVE-2026-81735(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 / 201× 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 353 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 253 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81735?
CVE-2026-81735 is a critical-severity vulnerability; its CVE record was published on August 27, 2026. startServer.ts in the mcp-http-server package of UI-TARS-desktop defaulted its listen address to '::' when no host was given, so startSseAndStreamableHttpMcpServer bound the Streamable HTTP and SSE MCP transports to every interface, and its authentication middleware was optional: middlewares are…
When was CVE-2026-81735 made public?
CVE-2026-81735 was made public on July 1, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 27, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-81735 actively exploited?
CVE-2026-81735 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-81735?
CVE-2026-81735 has a CVSS base score of 10.0 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-81735?
An upstream fix for CVE-2026-81735 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-81735 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-81735?

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

Book a Demo →Browse All CVEs