Managed service providers (MSPs) using ScreenConnect are facing a major threat: a vulnerability dubbed CVE-2026-84869 is being abused by attackers to push and execute malicious files on technicians’ machines without any confirmation prompt. This issue turns routine remote-support sessions into dangerous pathways, jeopardizing machines that often have access to customer systems, sensitive credentials, and internal management tools.
What is the Vulnerability?
The flaw lies in how ScreenConnect’s host clients handle file transfers from guests during Support and Access sessions. Thanks to this vulnerability, a guest can send over a file and have it execute automatically—no permission required. In one documented case, a technician opened an Access session and an attacker delivered a batch script that launched immediately from a temporary folder. From there, the malware used PowerShell to hide its activity, extracted Telegram connection settings, checked the OS version, assessed admin rights, and finally downloaded an installer. Rather than being installed normally, the package was extracted as an administrative image, leaving no typical install footprint.
Scope of the Exploitation
The CVE-2026-84869 issue carries a score of 9.9, signaling its severity. ConnectWise disclosed it on September 8, 2026, with CISA adding the vulnerability to its Known Exploited Vulnerabilities catalog days later. Reports from Huntress reveal that by November 12 attackers had used the flaw to deploy a rogue remote access client in just nine seconds after a technician connected. Between October 20 and November 16, over 688,000 guest attempts were recorded across 42 MSP ScreenConnect servers trying to execute batch files via 29 IP addresses. Not all attempts succeeded.
Indicators & Tactics Used
Attackers have employed several methods to remain undetected including disguising malicious clients with names mirroring legitimate components, for example posing as “Windows Update.” They’ve placed scripts in startup folders, used temporary batch scripts, and leveraged unrecognized relays. Key indicators of a compromised workstation include the presence of new scripts run by ScreenConnect, hidden PowerShell activity, odd startup entries, and unauthorized connections to unfamiliar domains or hosts.
What MSPs Must Do Now
Mitigation requires prompt action: update all ScreenConnect host clients to version 26.6.5 or newer, along with updating any affected Access agents. Simply upgrading servers isn’t enough—technicians’ machines must be patched too. In cases where immediate patching isn’t feasible, removing the “TransferFiles” permission from session groups and roles provides a stopgap. Investigations should focus on logs showing guest file transfers and execution, hidden PowerShell launches, unknown scripts in startup paths, and new remote clients disguised as system components. If confirmed compromised, isolate the machine, uninstall rogue software, and rotate all administrative and credential vault access related to management tools or customer systems.
This vulnerability is especially dangerous because it exploits remote support channels that are implicitly trusted. MSPs are uniquely exposed: once an attacker has control, lateral movement, credential theft, or persistent access to customer systems become possible. Ensuring strict permissions, visibility into session activity, and rapid patch management are no longer optional—they’re essential to prevent widespread damage.
Analytically, this incident underscores how supply-chain and third-party tool risks are evolving. Remote support platforms like ScreenConnect are foundational to how organizations operate—when exploited, they become potent attack vectors. The speed with which batch files can be executed, clients can be misrepresented as system components, and credential theft can follow reveals that adversaries are refining their playbooks faster than many defenses can adapt. For businesses and MSPs, this means reevaluating not just perimeter security, but visibility and control inside support tools. Watch for updates to access control policies, vendor security disclosures, and any signs of intrusion tied to remote-support software in your environment.