HomeTech NewsCybersecurityHuntress Finds ScreenConnect Flaw Exploited Against Technicians

Huntress Finds ScreenConnect Flaw Exploited Against Technicians

Huntress says a ScreenConnect client flaw, CVE-2026-84869, is being exploited against managed-service-provider technicians in a month-long spray of guest “run file” requests, and that it has confirmed one full compromise and one canary run.

In a blog published at 18:00 GMT on 16 November 2026, the firm wrote: “Since October 20, we’ve seen at least 688,000 guest “run file” requests for update*.bat hit 42 MSP ScreenConnect servers from 29 IP addresses, waiting for any technician to join.” Those 688,000 events are requests, not compromises, and 42 is the number of servers Huntress says it saw being hit, not a count of breached providers.

On 12 November, Huntress said, it observed “one managed service provider’s (MSP) technician’s workstation exploited to run a guest-pushed batch file,” which then messaged the operator, fetched an installer, and started a rogue ScreenConnect client pointing at the attacker’s own relay, “all in about 9 seconds.” On 13 November, “we observed a second technician’s client run an attacker “canary” file.” The operator is not named. TSN is not reproducing the domains, addresses or command lines from that write-up.

What ConnectWise fixed, and what still has to be done on the technician’s machine

ConnectWise disclosed the flaw on 8 September 2026. It described “a condition in the ScreenConnect client that may allow files to be transferred and executed through an active remote session without authorization or Host confirmation in certain circumstances.” The bulletin says “ScreenConnect servers are not impacted,” and gives the issue a CVSS score of 9.9. CISA added CVE-2026-84869 to its Known Exploited Vulnerabilities catalogue on 11 September 2026, with a due date of 14 September.

The fixed version is ScreenConnect 26.6.5. Huntress, echoing ConnectWise, says every technician’s host client, and any Access agents the vendor lists, should be updated to 26.6.5 or later. Updating the server alone does not close the hole, because the vulnerable code runs on the technician’s machine. ConnectWise tells cloud customers that, after the vendor has upgraded the server, they should still reinstall host clients and update Access agents, and gives on-premises partners the same client-side instruction once they have moved to 26.6.5.

If the update cannot be applied at once, ConnectWise’s interim step is to deselect the TransferFiles permission on roles and session groups. The bulletin is explicit that this “is not a substitute for installing the security update.”

Huntress also says administrators should look for a host client spawning scripts from its temporary folder. That is Huntress’s hunting advice, not a description of how to carry out the exploit.

Why this is not SCKit, and not a count of 42 breaches

Huntress separates this activity from two earlier ScreenConnect campaigns it has already described. The malware it calls SCKit, it says, “appears to be leveraging a vulnerable third-party extension on the server side of ScreenConnect and not directly exploiting CVE-2026-84869.” TSN has already covered partners being told to avoid sessions after that SCKit activity. The present spray, Huntress says, is distinct from a separate campaign it described on 13 November that planted unauthorised guest sessions using cryptocurrency-exchange names on “more than 100 MSP ScreenConnect servers.”

On the busiest server in this spray, Huntress says, “10 guest sessions from seven IPs made 70,414 requests over three weeks.” In October, it says, at least four more technicians were exposed to guest-pushed files, including a path-traversal attempt aimed at a technician’s Startup folder. Those are exposures Huntress recorded, not additional confirmed compromises.

The same remote-management setting that makes a technician’s workstation valuable is the reason the figures have to stay precise. TSN has also recently covered N-able’s advice on N-central after the 4EverAble2Shell chain, Microsoft’s account of activity after a ConnectWise-related incident, and a separate ConnectWise cloud-backup breach involving Microsoft 365. Those are different products and different cases.

A spray of requests is not a count of compromises

The number that will travel furthest, 688,000, is a count of guest “run file” requests that Huntress says it saw against 42 servers from 20 October. It is not a count of successful takeovers, and it is not a statement that 42 MSPs were breached. Huntress’s confirmed outcomes in this write-up are narrower: one technician workstation fully compromised on 12 November, and one canary file executed on a second technician’s client on 13 November. The firm also describes earlier exposures and a near-miss. Those layers should not be collapsed into a single breach tally.

The link from the spray to the 12 November compromise is Huntress’s own assessment. It says it has “high confidence” that the spray operator and the operator behind that compromise are the same, based on the overlap it saw in file names and timing. That is a Huntress judgement, not an attribution published by ConnectWise or CISA, and this article leaves the operator unnamed because Huntress did.

The patch story is older than the spray Huntress is now describing. CVE-2026-84869 has been in CISA’s KEV catalogue since 11 September, and the fixed client has been 26.6.5 since 8 September. Huntress says many technicians in the cases it reviewed were still on older client versions weeks after that fix shipped. The TransferFiles workaround is only an interim control, and ConnectWise has already said it is not a substitute for the update. None of that is a finding that every unpatched client in the spray was compromised.

Sources

Related stories

Follow @tsnmediahub on X for breaking AI news as it happens.

Follow on X

Share this story

Latest stories

More in this category

Latest stories

Explore the TSN Atlas: Every topic we cover, mapped. Click a bubble to dive in.