ConnectWise in 2026: ScreenConnect CVE-2026-84869 and the Cloud Backup incident
ConnectWise sells ScreenConnect, a remote-support tool that managed service providers (MSPs) use to reach their customers' machines, so a flaw in it reaches far past ConnectWise. This page keeps product vulnerabilities apart from incidents at ConnectWise itself.
Short answer
Was ConnectWise hacked?
CVE-2026-84869 is not a breach of ConnectWise: it is a vulnerability in the ScreenConnect client, fixed in 26.6.5 on 8 September 2026 and listed by CISA as known exploited. ConnectWise says a condition in the client "may allow files to be transferred and executed through an active remote session without authorization or Host confirmation in certain circumstances", and that servers are not impacted. On 16 November 2026 Huntress reported attackers using it against MSP technicians.
Separately, ConnectWise did report an incident of its own. Microsoft says ConnectWise published an initial advisory on 16 October 2026 about attempted unauthorized access associated with its Cloud Backup application, and Microsoft assesses that the actor it tracks as Storm-0940 was responsible. Microsoft says the presence of an affected app or a successful sign-in does not necessarily mean customer data was accessed.
Timeline at a glance
8 Sep 2026ConnectWise fixes CVE-2026-84869 (ScreenConnect client, CVSS 9.9) in 26.6.5; servers not impacted. (ConnectWise)Not a breach
11 Sep 2026CISA adds CVE-2026-84869 to the Known Exploited Vulnerabilities catalog. (CISA)Not a breach
16 Oct 2026ConnectWise advisory on attempted unauthorized access associated with Cloud Backup; Microsoft later attributes it to Storm-0940. (Microsoft)Confirmed
11 Nov 2026SCKit: rogue ScreenConnect clients on at least 288 endpoints in 48 organisations; Huntress links it to a third-party extension, not the CVE. (Huntress)Reported
16 Nov 2026Huntress reports CVE-2026-84869 used against MSP technicians; 42 MSP servers sprayed since 20 October. (Huntress)Not a breach
Last updated 18 November 2026. Every entry is dated and linked to its source; claims by attackers are labelled as claims, never stated as fact.
ConnectWise incident timeline, in detail
Confirmed = acknowledged by ConnectWise, a regulator filing or a court. Reported = credible reporting ConnectWise has not fully confirmed. Unverified claim = an attacker or leak-site claim.
Sep-Nov 2026Not a breachProduct vulnerability (client side), known exploited
CVE-2026-84869: ScreenConnect client runs files pushed through a session
What happened. ConnectWise's 8 September advisory covers all ScreenConnect versions before 26.6.5 (CVSS 9.9, CWE-862 and CWE-269). The vulnerable code runs on the technician's host client, so updating the server alone does not fix it. Temporary mitigation: remove the TransferFiles permission. CISA added it to KEV on 11 September with the forensic-triage flag.
Impact. Huntress reports about 688,000 guest "run file" requests against 42 MSP servers from 29 IP addresses between 20 October and 16 November, one technician fully compromised on 12 November and a canary file run on 13 November. No named actor.
What happened. Microsoft says ConnectWise published an initial advisory on 16 October 2026 about attempted unauthorized access associated with Cloud Backup, and that the actor acquired control of the identities of multiple ConnectWise cloud applications. Microsoft assesses Storm-0940 was responsible.
Impact. Microsoft says the presence of an affected app or successful authentication "does not necessarily indicate that customer data was accessed or exfiltrated." It does not link this incident to ScreenConnect.
Threat digests describe CVE-2026-84869 as "exploited to install rogue ScreenConnect clients". Huntress traced the August rogue clients to social engineering and says the November SCKit wave is "not directly exploiting CVE-2026-84869"; the CVE exploitation it reports targets technicians' own clients.
ConnectWise's advisory does not say whether the flaw was exploited; the exploitation evidence is CISA's KEV listing and Huntress's reporting.
The pattern across the record
Remote-support tools are a path into every customer
A technician's ScreenConnect client is trusted by every machine that MSP supports, so a flaw on the technician side reaches all of them.
Client and server patch separately
Cloud customers get server fixes automatically; host clients and access agents still have to be updated on each machine.
What it means for ConnectWise customers — and what to do
If you or your MSP use ScreenConnect, check the clients, not just the server.
1.Update every host client
Move technician host clients and Access agents to 26.6.5 or later. Until then, remove the TransferFiles permission from roles and session groups.
2.Ask your MSP
Ask which ScreenConnect version their technicians run and whether they used the third-party extensions ConnectWise disabled in November.
CVE-2026-84869 is a product flaw, not a breach. Separately, ConnectWise reported attempted unauthorized access associated with its Cloud Backup application in October 2026, which Microsoft attributes to Storm-0940.
Which ScreenConnect version fixes CVE-2026-84869?+
26.6.5 or later. Every version before 26.6.5 is affected, and the fix has to reach the technician host clients and access agents, not only the server.
Is CVE-2026-84869 exploited?+
Yes, per CISA, which added it to KEV on 11 September 2026. Huntress reported exploitation against MSP technicians in October and November 2026.
Is the SCKit campaign the same thing?+
No. Huntress says SCKit appears to use a vulnerable third-party server extension and is not directly exploiting CVE-2026-84869, although it sets a trap for technicians who connect later.
Independent analysis for security-leadership education; not affiliated with or endorsed by ConnectWise. Facts are attributed to the dated sources above, and anything disputed or unconfirmed is labelled as such. See the full Breach Index.