Skip to content
All posts

ScreenConnect CVE-2026-84869 Exploited: What MSPs Do Now

November 18, 2026 · Team PlayCISO
TL;DR · the short version

CVE-2026-84869 (CVSS 9.9) is a flaw in the ConnectWise ScreenConnect client, the host client a technician runs, that ConnectWise says may let files be transferred and executed through an active remote session without authorization or Host confirmation. Every version before 26.6.5 is affected; ConnectWise says servers are not. CISA added it to the Known Exploited Vulnerabilities catalog on 11 September 2026. On 16 November Huntress reported attackers spraying 42 MSP ScreenConnect servers with guest "run file" requests so that a technician who joins a session runs the file, with one technician fully compromised on 12 November. Separate campaigns installed rogue ScreenConnect clients by other routes: Huntress says the November SCKit wave appears tied to a third-party server extension and "not directly exploiting CVE-2026-84869". Update every technician host client to 26.6.5 or later, inventory remote-access tools and hunt for ScreenConnect clients that are not yours.

Put it into practice
Rank this against everything else on your patch list
Check the KEV entry, due date and forensic-triage flag, then score it with the rest of your backlog.
Open the KEV checker

If your managed service provider, or your own IT team, uses ConnectWise ScreenConnect, the version that matters this week is the one on each technician's laptop. CVE-2026-84869 is a flaw in the ScreenConnect client. It is fixed in 26.6.5, it has been in CISA's Known Exploited Vulnerabilities catalog since 11 September 2026, and on 16 November Huntress reported attackers using it against MSP technicians.

Who this is for: MSPs, IT teams that run their own ScreenConnect, and security leaders whose suppliers have remote access into their estate.

Based on ConnectWise's 8 September advisory, the NVD record, the CISA KEV feed (read 18 November 2026) and Huntress's September, 11 November and 16 November posts. PlayCISO is not affiliated with ConnectWise or Huntress. Facts as reported on 18 November 2026.

Confirmed vs not yet known

Confirmed by ConnectWise: the flaw is in the ScreenConnect client; all versions before 26.6.5 are affected; 26.6.5 fixes it; servers are not impacted; CVSS 9.9.

Confirmed by CISA: listed as known exploited on 11 September 2026, due 14 September, forensic triage required under BOD 26-04. Known ransomware use: unknown.

Reported by Huntress (16 Nov): guest "run file" spraying against 42 MSP servers from 20 October to 16 November; one technician fully compromised on 12 November; a canary file run on another technician's machine on 13 November. No named actor.

Not established: that the rogue ScreenConnect clients seen in August and in the November SCKit waves were installed through this CVE. Huntress says the SCKit wave is "not directly exploiting CVE-2026-84869". ConnectWise's advisory does not discuss exploitation.

What CVE-2026-84869 is

ConnectWise's advisory says: "A condition in the ScreenConnect client may allow files to be transferred and executed through an active remote session without authorization or Host confirmation in certain circumstances. ScreenConnect servers are not impacted." The NVD record lists the weaknesses as CWE-862 (missing authorization) and CWE-269 (improper privilege management), and ConnectWise scores it 9.9.

The direction is what surprises people. In a ScreenConnect session the Host is the technician and the Guest is the machine being supported. Huntress describes the risk as a guest pushing a file that the technician's own client runs. Its summary: "Updating the server alone doesn't fix this, because the vulnerable code runs on the technician's machine." A compromised technician laptop usually holds the keys to every customer that MSP supports.

What Huntress reported in November

  • Spraying MSP servers. Between 20 October and 16 November, 42 MSP ScreenConnect servers received about 688,000 guest "run file" requests for update*.bat files from 29 source IP addresses. The busiest server logged 70,414 requests in three weeks.
  • A technician compromised. Huntress says a technician at one MSP was fully compromised on 12 November.
  • A canary. On 13 November a technician at another MSP joined a session and the guest pushed a harmless text file, which the client opened. Huntress calls it a "classic canary" to confirm the technique works before sending anything harmful.
  • No named actor. Huntress does not attribute the spraying to a known group.

Rogue ScreenConnect clients: three different stories

Threat digests summarised all of this as "CVE-2026-84869 exploited to install rogue ScreenConnect clients". The sources describe three separate things:

StoryHow the rogue client got thereLink to CVE-2026-84869
August-September worm-like rogue clients (Huntress)Social engineering: a Quick Assist tech-support scam, a phished ScreenConnect installer, a fake refund form. Modified clients then pushed the same scripts to new Host sessions.Discussed in Huntress's 8 September update as the file-transfer flaw; Huntress does not say the first installs used it.
SCKit, 11 and 13 November (Huntress)Run commands on cloud-hosted panels installed rogue clients and session-cookie relays: at least 288 endpoints in 48 organisations in the first wave, 205 hosts in 41 in the second. Huntress links it to a third-party extension, RMM+.Huntress: "not directly exploiting CVE-2026-84869", but staging a "relay trap" for technicians who connect later.
Technician exploitation, 20 Oct-16 Nov (Huntress)No rogue client needed: the attacker joins as a guest and the technician's unpatched client runs the file.Yes, per Huntress.

Huntress quotes ConnectWise as saying it identified five third-party extensions that may be associated with the SCKit activity and disabled them on hosted environments, and that on-premises partners should disable them themselves.

Useful next, if this was relevant to you

Showing 1 of 3: Breach Cost Calculator

Timeline

Date (2026)WhatSource
20 and 24 AugHuntress handles incidents with rogue ScreenConnect clients across unrelated organisationsHuntress
8 SepConnectWise publishes the advisory and ScreenConnect 26.6.5; CVE-2026-84869 publishedConnectWise, NVD
11 SepCISA adds CVE-2026-84869 to KEV, due 14 SepCISA KEV
20 Oct-16 NovGuest "run file" spraying against 42 MSP serversHuntress
11 NovSCKit wave: rogue clients and cookie relays on at least 288 endpoints in 48 organisationsHuntress
12 NovA technician at one MSP fully compromisedHuntress
13 NovCanary file run on a second MSP technician's machine; second SCKit wave (205 hosts, 41 organisations)Huntress, Huntress
16 NovHuntress publishes the technician exploitation reportHuntress

What security leaders should do this week

  1. Patch every client, not just the server. Update every technician's ScreenConnect host client, and any Access agents ConnectWise lists, to 26.6.5 or later. Cloud customers: ConnectWise says no server action is needed, but the clients still need updating. If you cannot update today, remove the TransferFiles permission from roles and session groups, as ConnectWise advises.
  2. Ask your MSP. Ask in writing which ScreenConnect version their technicians run, whether they used RMM+ or the other extensions ConnectWise disabled, and whether they have reviewed guest file-run events since 20 October.
  3. Inventory remote-access tools. List every remote monitoring and management (RMM) and remote-support tool on your endpoints and who owns each instance. Anything nobody can explain is a finding.
  4. Block unapproved RMM. Use application control and egress rules so that only your approved ScreenConnect instance (and relay host) can run and connect. A ScreenConnect client that talks to someone else's server is not yours, whatever the binary's signature says.
  5. Hunt. Look for new ScreenConnect services or a second ScreenConnect client on one machine, clients pointing at relay hosts you do not run, scripts launched from ScreenConnect temp folders on technician machines, new Startup entries, and guest-originated file-run events in session history while a host was connected. Huntress advises not to connect to a suspect machine through ScreenConnect to investigate it.
  6. If you find one: isolate the machine, remove the rogue client and its persistence, and rotate every credential reachable from it. Huntress notes that isolation alone does not remove persistence. KEV marks this CVE for forensic triage, so keep evidence before you reimage.

To weigh it against the rest of your backlog, use the KEV checker and the vulnerability prioritizer. For the supplier side, the third-party breach response checklist covers what to ask an MSP, and the identity compromise checklist covers the credential rotation.

Is this a ConnectWise breach?

No. CVE-2026-84869 is a product vulnerability. ConnectWise did report a separate October 2026 incident involving its Cloud Backup application, which Microsoft attributes to Storm-0940; our ConnectWise Breach Index page keeps the two apart. See also our 17-18 November incident roundup.

FAQ

What is CVE-2026-84869?

A flaw in the ConnectWise ScreenConnect client. ConnectWise says "a condition in the ScreenConnect client may allow files to be transferred and executed through an active remote session without authorization or Host confirmation in certain circumstances." It is rated CVSS 9.9 and classed as missing authorization (CWE-862) and improper privilege management (CWE-269). ConnectWise says ScreenConnect servers are not impacted.

Which ScreenConnect versions are affected by CVE-2026-84869?

All versions before 26.6.5, per ConnectWise and the NVD record. The fix is ScreenConnect 26.6.5 or later. Because the vulnerable code is in the client, the technician host clients and any Access agents ConnectWise lists must be updated, not only the server.

Is CVE-2026-84869 in CISA KEV?

Yes. CISA added it on 11 September 2026 with a due date of 14 September and the forensic-triage flag set under BOD 26-04. Known ransomware use is listed as unknown.

Is CVE-2026-84869 being exploited?

CISA lists it as known exploited. On 16 November 2026 Huntress reported guest "run file" spraying against 42 MSP ScreenConnect servers between 20 October and 16 November (688,000 requests from 29 IP addresses), a technician fully compromised on 12 November and a canary file run on another technician's machine on 13 November. ConnectWise's own advisory does not say whether the flaw was exploited.

Was CVE-2026-84869 used to install the rogue ScreenConnect clients?

Not as far as the sources say. Huntress's September report traced rogue clients to social engineering (a Quick Assist scam, a phished installer, a fake refund form). Its 11 November SCKit report says the wave "appears to be leveraging a vulnerable third-party extension on the server side of ScreenConnect and not directly exploiting CVE-2026-84869", while staging a relay trap for technicians who connect later.

Is there a workaround if we cannot patch CVE-2026-84869 today?

ConnectWise says to remove the TransferFiles permission from roles and session groups (Administration > Security > Roles) until you can update, and says this is not a substitute for the update.

Was ConnectWise breached?

CVE-2026-84869 is a product vulnerability, not a breach of ConnectWise. Separately, ConnectWise published an advisory on 16 October 2026 about attempted unauthorized access associated with its Cloud Backup application, which Microsoft assesses was the work of Storm-0940. Our Breach Index page for ConnectWise keeps the two apart.

Sources

As of 18 November 2026. Counts are Huntress's and may rise; re-check the KEV entry and ConnectWise's bulletin for changes.

Rank this against everything else on your patch list
Check the KEV entry, due date and forensic-triage flag, then score it with the rest of your backlog.
Open the KEV checker
Take this with you
What CVE-2026-84869 is · What Huntress reported in November · Rogue ScreenConnect clients: three diffe… · Timeline · What security leaders should do this week · Is this a ConnectWise breach?

Ready to practise the decisions these articles describe?

Run your first Cyber War Room free →

Pro