Skip to main content

Attackers Are Using a Patched ScreenConnect Flaw to Run Scripts on MSP Technicians’ Own Computers

Huntress says 42 MSP ScreenConnect servers took more than 688,000 file-run requests in a month. The fix for CVE-2026-84869 is on the technician's client, not just the server.

A clean and modern office desk with dual monitors and ergonomic chairs, ideal for productivity.
KBY News Desk8 min read

In this article

Share

Attackers have spent a month sending hundreds of thousands of file-run requests at ScreenConnect servers run by managed service providers, trying to make technicians’ own machines execute a script the moment they join a support session. Huntress, the security firm that documented the campaign on Monday 16 November, says 42 servers were hit with more than 688,000 requests from 29 source addresses since 20 October. The flaw behind it, CVE-2026-84869, was fixed by ConnectWise on 8 September, and the fix has to be applied on the technician’s computer, not only on the server.

That last point is the one most likely to catch an MSP out. If your team updated the ScreenConnect server in September and stopped there, you may still be exposed today.

#What the bug lets a guest do

CVE-2026-84869 carries a CVSS score of 9.9 and is described by SecurityWeek as a missing authorisation and improper privilege management flaw. Per Huntress’s reading of ConnectWise’s advisory, it affects Support and Access sessions: a guest, meaning the customer or anyone who has joined the session as a guest, can trigger a file transfer that the technician’s host client then runs without asking for authorisation or confirmation, including with elevated rights. CISA added the vulnerability to its Known Exploited Vulnerabilities catalogue on 11 September, according to both SecurityWeek and Huntress.

Think about what that means in an MSP. The technician’s workstation is usually the most privileged machine in the business: it holds sessions, saved credentials and a route into many customers. A bug that turns a joined support session into code execution on that workstation does not compromise one customer. It compromises the provider and, through the provider, every customer the technician can reach.

#A month of requests, and nine seconds to compromise

Huntress says the activity it has tracked since 20 October is a flood of guest “run file” requests naming a batch script called update-something.bat. The busiest single server saw 70,414 requests over three weeks, coming from just ten guest sessions. SecurityWeek, summarising the same research, describes more than 40 servers and over 688,000 requests.

The pattern Huntress describes is simple. A malicious guest sits in a session, often one with a blank name, and pushes the file. Nothing happens until a technician joins. At that point the technician’s host client runs the file with no prompt. Huntress says the script reports back to the attacker, pulls down a rebranded copy of the ScreenConnect client, and connects it to the attacker’s own relay, which gives them a remote-control foothold that looks like ordinary remote-support software. In one case Huntress timed the whole chain, from the technician joining to the rogue client connecting, at about nine seconds, on 12 November at 16:46 UTC.

Huntress also saw an earlier variant in October aimed at three technicians that tried to place a script in the Windows Startup folder through a path trick, so that it would run at the next login. We would read that as the attackers trying more than one route to the same result while they worked out which one reliably landed.

SecurityWeek adds context: it links an earlier Huntress warning saying exploitation of this flaw started on 20 August, which is roughly three weeks before ConnectWise shipped a fix. We have not read that earlier warning, so we are repeating SecurityWeek’s description of it, not confirming it.

#Why updating the server was not enough

ScreenConnect is a server you host plus a client that technicians run. The vulnerable behaviour is in the host client, the program on the technician’s machine that receives the file and runs it. Huntress states plainly that updating the server alone does not fix this, and that the fixed host client version is 26.6.5 or later. SecurityWeek reports the same fixed version and adds that the Access agents ConnectWise lists need updating as well.

Huntress found technicians still running much older clients weeks after the fix: versions it identifies as 22.x, 24.2 and 25.8. That is the realistic picture of an MSP estate. Technicians install the client once, it works, and nobody puts “check the client version on every laptop” on a patch schedule, because the server is the thing everyone thinks of as ScreenConnect.

If you cannot update every client straight away, Huntress says ConnectWise’s interim mitigation is to remove the TransferFiles permission from roles that do not need it.

#Our view: this is a patching-process failure, not a surprise

We think the interesting part of this story is not the exploit. It is that a flaw fixed on 8 September, added to CISA’s catalogue three days later, was still being used successfully ten weeks on against providers whose job is to keep other people’s software up to date. In our view that makes it a good test for any MSP, and any in-house IT team that uses ScreenConnect to support staff: could you, today, list every technician workstation and the client version on it? If the answer is “we would have to ask people”, the gap Huntress describes is open in your estate too.

There is also a design lesson. Remote-support tools are built to run things on machines. Any feature that lets the other party in a session push a file should be treated as a privileged capability, off by default and granted by role. Removing TransferFiles where nobody needs it is cheap, takes effect quickly, and would have blunted much of this campaign. We would do it even for teams that are fully patched.

Finally, an expectation, labelled as ours: because the requests are being made at this volume and the technique is now published, we expect the pool of attackers to widen, and for other remote-support platforms to see similar guest-initiated file attacks. We would be wrong if Huntress and others report the traffic stopping once the older clients age out.

#Who is affected, and who can stop reading

You are in scope if you run ScreenConnect (Support or Access sessions) and any technician uses a host client older than 26.6.5. That includes MSPs, but equally an internal service desk that uses ScreenConnect to support staff. If you only ever connect to a ScreenConnect server that someone else runs, as an end user joining a session, this particular campaign is not aimed at you, although the technician on the other end is the target.

#What to check this week

Huntress’s guidance, which we have trimmed to the steps most teams can act on, runs roughly like this:

  1. Update every technician’s host client to 26.6.5 or later, and every Access agent ConnectWise lists. Check the version actually installed on each laptop, not the server’s.
  2. Where that cannot happen today, remove the TransferFiles permission from roles that do not need it.
  3. Search the server’s session database for file-run and file-sent events coming from guest connections. Huntress points to the Session.db file, which it advises working on from a copy, and to event types 85 (run file) and 86 (sent file) with a guest process type, especially batch files named update-something in sessions with blank names. Treat any path containing “../” as suspect.
  4. On technician endpoints, look for the ScreenConnect Windows client launching a command shell, PowerShell or a script host from a temporary folder, and for outbound connections to relay servers you do not recognise, often on port 8041.
  5. If you find a hit, isolate the machine, remove the rogue client, and rotate every credential reachable from it: remote monitoring and management, professional services automation, ScreenConnect, password vaults and customer admin accounts. Restrict who can join sessions as a guest and limit who can reach the web interface and installer, for example by IP address or VPN.

Huntress publishes file names, a file hash and a relay address for matching. We have not reproduced them here. Take them from the Huntress post itself, and verify them before you build detections from them, because we have read the post rather than tested the indicators.

#What we do not know yet

Neither Huntress nor SecurityWeek says who is behind the campaign, and we will not guess. The sources we read do not say how many of the 42 targeted servers were actually compromised, as opposed to receiving requests, and they do not name any affected provider. We were also unable to read ConnectWise’s own bulletin for CVE-2026-84869, which blocked our automated request, so everything above about its contents comes from Huntress and SecurityWeek and should be checked against the bulletin. We will update this story if ConnectWise or Huntress add numbers, indicators or a change in the advice.

The practical takeaway is short. If your technicians use ScreenConnect, check the client version on their machines before the end of the week, and turn off file transfer for anyone who does not need it.

Evidence trail

Sources and verification

Primary documentation and external technical references used in this article.

  1. 01Huntress: CVE-2026-84869 in ScreenConnect exploited to run malicious files on MSP technician accountshuntress.com
  2. 02SecurityWeek: MSP ScreenConnect servers targeted in month-long campaignsecurityweek.com

About this page

Credited to

Dates

Published

Corrections

No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.

Reader Interaction

Comments

Add a thoughtful note on Attackers Are Using a Patched ScreenConnect Flaw to Run Scripts on MSP Technicians’ Own Computers. Comments are checked for spam and held for moderation before appearing.

Loading comments...

More news

All news

Was this useful?

Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.

Get new fixes by email.

New runbooks, configuration traps and fixes from KBY Technologies, about twice a week.