ConnectWise ScreenConnect: client vulnerability (CVE-2026-84869) allows code execution, fixed in 26.6.5
Published 17/11/2026 12:52
Timeline
4 events over 5 d 12 h
- 11/11/2026 23:56First report+2 h
- 12/11/2026 02:28CorroboratedCommunity post+5 d 9 h
- 17/11/2026 12:27ConfirmedBSI CERT-Bund (WID)+25 min
- 17/11/2026 12:52Published on WatchtowerPro CISO
In short
An attacker who can join a ScreenConnect support session can push files to a technician's computer and run them, even with elevated rights. Affected are ScreenConnect clients before 26.6.5, not the server. Update technician host clients and Access agents to 26.6.5 or later, and update on-premise servers. Huntress reports exploitation against MSP technicians. Shodan estimates 8,348 internet-facing systems tagged with CVE-2026-84869 worldwide, 2,835 of them in the EU (19/11/2026).
How bad is it
Critical. An attacker who can join a remote support session can push a file to a technician's computer and have it run automatically, without any prompt or approval.
Being exploited - on CISA's known-exploited list since 11/09/2026.
Severity score
CVSS 3.1 from NVD, from the vendor, read 19/11/2026.
What an attacker needs
- Internet access to itEnough
- A loginA user account
- A user to clickNo
- Special settingsNo
Red helps the attacker, blue holds them back, grey is not published yet.
If it works, an attacker can
- Run their own code on the system
- Read the data it holds
- Change or delete that data
- Take it offline
Type: remote code execution.
A score is the worst case for the flaw, not a verdict on any one system. How we score · ReconX customers see which of their own systems are affected.
Affected versions
- ScreenConnect, all versions prior to 26.6.5 (per the CVE record).
- ConnectWise says Client Support and Access sessions are affected. The flaw is in the client, not the server.
- Technician workstations that join sessions with an unpatched client are exposed. Huntress says the technician only has to join the session, which can be attacker-controlled or a real customer session the attacker has joined.
Fixed in
- 26.6 branch: 26.6.5
What to do now
- Update on-premise ScreenConnect servers to 26.6.5 or later. Cloud servers are already updated according to ConnectWise, so no server action is needed there.
- Update every technician host client and Access agent to the fixed version, not only the server. Huntress gives the same advice.
- Automate-integrated deployments can be updated through Automate Product Updates if the Automate Assurance subscription is active. Out-of-maintenance licences must be renewed or upgraded before installing the latest release.
- Until updated, in Administration > Security > Roles edit each role, review each session group, untick TransferFiles and save. This reduces exposure and does not make a system safe.
- Hunt for Huntress IOCs and treat any hit as a compromised technician machine: domain masterdarky[.]com (194.15.36[.]33); files update.bat, update_<8hex>.bat, marker.txt, Sync.bat, Run-Lateral.bat, svc_payload.cmd; path %LOCALAPPDATA%\wclient_<8hex>\Windows Update Agent\WindowsUpdate.WindowsClient.exe; SHA-256 f8871b1561d5c77c297378a7f49c84de52a01ff297395544f0e95d13ef972841. The 14 sprayer IPs are listed in the Huntress post.
ReconX customers see the full notice - and their own systems
Our customers are alerted at every phase. Until a patch exists, the ReconX agent watches their servers from the inside for anomalies, and our outside view - the attacker's view - shows which systems to fix first.
In ReconX: the full analysis, 5 open questions, followed up as sources answer and all 7 sources with their dates. And technology matching: which of your systems run ConnectWise ScreenConnect, at which version, fixed or not - and what each one needs.
Main sources
[UPDATE] [kritisch] ConnectWise ScreenConnect: Schwachstelle ermöglicht Codeausführung CERT · Active ScreenConnect attacks breach MSPs, impact dozens of organizations Research · SCKit Worm Installs Rogue ScreenConnect Clients and Session Cookie Relays Across Hundreds of Endpoints Research