Exploitation of Vulnerability in ConnectWise ScreenConnect Poses Serious Security Threat
Recent cybersecurity revelations have illuminated a significant vulnerability dubbed CVE-2026-84869, which is being exploited by cybercriminals to compromise technicians’ workstations using ConnectWise ScreenConnect. This vulnerability allows attackers to execute malicious files easily and establish unauthorized remote access on targeted systems, posing a grave risk to managed service providers (MSPs).
According to security firm Huntress, a notable incident occurred on November 12, when an attack was confirmed. In this case, a technician was tricked into joining a malicious session, where a guest-pushed batch file initiated a series of actions that were completed in a mere nine seconds. The batch file was designed to notify a Telegram bot, download an installer, and create a rogue ScreenConnect connection, all without the technician realizing any deviation from normal operations.
The nature of this vulnerability is particularly alarming. It allows a technician to unwittingly join a compromised session, triggering the vulnerable host client to execute unauthorized file-execution requests without even showing a confirmation prompt. Such a lapse can lead to catastrophic data breaches, especially when technicians typically have access to sensitive information like customer credentials and management consoles.
ConnectWise, the company behind ScreenConnect, disclosed this vulnerability on September 8, 2026, and assigned it a CVSS score of 9.9, indicating severe risk. Their security advisory outlines weaknesses stemming from missing authorization and improper privilege management affecting clients prior to version 26.6.5. The main consequence of this flaw is the facilitation of unauthorized file transfers and execution through active sessions, although the ScreenConnect servers themselves remain unaffected.
In the November 12 attack, Huntress observed that the MSP technician inadvertently joined an access session lacking any distinctive name. In this instance, the vulnerable host executed a file named update_224ac089.bat from its temporary directory. The script employed various methods, including PowerShell and WScript.Shell, to obfuscate its actions. It decoded Telegram notification credentials, queried Windows version information, checked for installed rogue clients, and even examined administrative privileges. Following these checks, the script downloaded an installer from a potentially malicious website, masterdarky[.]com, continuing the stealthy operation.
This installer, an administrative MSD extraction package, placed its payload in a local directory without leaving a trace in the conventional installation records. After activating the Secondary Logon service, the script proceeded to execute a renamed ScreenConnect client dubbed WindowsUpdate.WindowsClient.exe, which connected back to the attackers on a specific port. By masquerading as a Windows Update client, this unauthorized access channel went unnoticed by the technician, thereby allowing attackers to infiltrate workstations that might contain sensitive customer information.
Huntress outlined a broader pattern of exploitation, with evidence showing at least 688,000 guest "run file" requests across 42 MSP ScreenConnect servers between October 20 and November 16. These requests typically entailed batch files labeled update.bat or update_<8hex>.bat, waiting for technicians to unknowingly connect to compromised sessions. The exact batch file associated with the confirmed breach had appeared across five different MSP servers, indicating a coordinated attack that began about 43 minutes prior to the execution of the malicious file.
The threat posed by this campaign lies in its strategy of targeting technicians at managed service providers rather than aiming directly at ScreenConnect servers. On November 13, another incident was confirmed wherein a technician’s client opened an attacker-supplied marker.txt file in Notepad++, signaling further infiltration efforts.
In addition to this, earlier activities noted on the servers included traversal requests targeting Sync.bat files located in technicians’ Windows Startup folders, although no sustained infections were identified from these attempts. Notably, this pattern diverges from other investigations conducted by Huntress, which found unauthorized sessions on over 100 servers without any confirmed guest-side malicious executions.
To safeguard against such vulnerabilities, MSPs are strongly advised to update all technician host clients and the affected Access agents to version 26.6.5 or later. Merely upgrading server infrastructure is insufficient, as it does not automatically remove vulnerabilities from endpoint clients. In scenarios where immediate patching cannot be applied, ConnectWise has recommended disabling TransferFiles permissions across relevant roles and session groups.
For investigators reacting to potential breaches, it is imperative to correlate guest-originated RunFile and SentFile database events with active technician connections. Inspecting workstation telemetry for ScreenConnect that could spawn scripts from temporary document files is equally crucial. Key indicators of compromise include unexpected startup scripts, directories associated with rogue clients, and connections to unfamiliar relay servers.
In conclusion, the sophistication of this attack underscores the need for immediate security measures. If a compromise is confirmed, affected workstations should be isolated, rogue clients removed, sessions revoked, and all accessible credentials rotated. Investigators should also preserve relevant telemetry and session evidence prior to any cleanup actions. As cybersecurity threats continue to evolve, vigilance remains paramount for organizations relying on remote access tools.

