If an outside IT provider supports your business, there is a good chance it uses ConnectWise ScreenConnect to reach your computers. On November 16, 2026, the security firm Huntress reported that attackers have exploited a ScreenConnect flaw, CVE-2026-84869, against IT providers’ own technicians. The fix has been out since September 8. The question for you is not technical. It is whether your provider applied it everywhere it needs to be, and you can ask that in one email.
The detail that makes this different: updating the ScreenConnect server is not enough. The vulnerable code runs in the client on the technician’s own PC. A provider can be fully patched on paper and still have technicians on old clients, which is what Huntress says it found.
What happened
ConnectWise published its security bulletin for ScreenConnect 26.6.5 on September 8, 2026. It describes a condition in the ScreenConnect client that “may allow files to be transferred and executed through an active remote session without authorization or Host confirmation in certain circumstances.” ConnectWise rates it 9.9 on the CVSS scale, says versions before 26.6.5 are affected and ScreenConnect servers are not, and gives Priority 1, its highest, recommending installation “within days.” For cloud customers it says no server action is required, but after upgrading partners must “reinstall your host clients and update your access agents.” As a temporary step, it says to remove the TransferFiles permission from roles.
CISA added CVE-2026-84869 to its Known Exploited Vulnerabilities catalog on September 11, with a federal due date of September 14, and marks it for forensic triage.
What Huntress found
Huntress’s November 16 report says it confirmed in-the-wild exploitation in which a guest in a remote session pushed a file that the connecting technician’s host client then ran, with no prompt on the technician’s screen. Its main findings:
- On November 12, a technician at one IT provider joined a blank-named session. Within about nine seconds, a guest-pushed batch file had run, reported to the attacker and installed a rebranded ScreenConnect client pointing at the attacker’s own server, named to look like Windows Update.
- On November 13, a second technician’s client ran a harmless “canary” text file, which Huntress reads as a test that the exploit works.
- Since October 20, Huntress counted at least 688,000 guest “run file” requests for batch files across 42 IT providers’ ScreenConnect servers, from 29 IP addresses, sprayed in the hope a technician would join.
- Many technicians were still on 22.x, 24.2 and 25.8 clients weeks after the fix shipped.
Huntress recommends updating every technician’s host client to 26.6.5 or later, hunting for the client launching scripts from its temporary folder, and, where a hit is found, rotating every credential reachable from that technician’s workstation. Its reasoning is the part business owners should read twice: a technician’s PC typically holds remote management consoles, saved credentials and access to every customer.
A separate campaign the same week
On November 13, Microsoft published research on a campaign it calls SCKit, which it says ConnectWise first reported on November 11. Attackers gained unauthorized access to IT providers’ cloud-hosted ScreenConnect instances, used it to install unauthorized remote-access clients on managed computers, and deployed a component designed to deliver a payload to a technician who connects. Microsoft says ConnectWise’s advisory describes an authentication flaw in versions 1.0.31 and 1.0.32 of the third-party RMM+ extension, which accepted an empty key when none was set, and that the entry method is still under investigation. Its guidance is to keep the identified extensions disabled and to investigate technician workstations and downstream computers, because removing a rogue client alone does not remove the toolkit’s persistence. Huntress says SCKit does not appear to exploit CVE-2026-84869 directly.
What it means for CFOs and CISOs
For a business that buys IT support, this is a vendor-management problem. Your provider’s remote-access tool is, in effect, a key to every computer it manages, including yours. You do not need to understand the exploit. You need a written, dated answer that the key is looked after, and you need to know what your contract says the provider must tell you after an incident.
This also shows up in paperwork. Cyber insurance applications and client security questionnaires increasingly ask how third parties with remote access are controlled. “Our MSP handles it” is not an answer an underwriter can score. “Our MSP confirmed in writing on November 19 that all technician clients are on 26.6.5 or later and the RMM+ extensions are disabled” is.
What to do this week
- Find out what your provider uses. Ask which remote-access tool it uses to reach your machines. If it is not ScreenConnect, ask the same questions about the tool it does use.
- Send these questions in writing. “Are all of your technicians’ ScreenConnect host clients and access agents on version 26.6.5 or later, and when was that confirmed? Are the RMM+ and Labtech Plus extensions disabled on your ScreenConnect instance? Have you checked our computers for ScreenConnect clients you did not install? Who can join a session as a guest, and is the web console restricted by IP or VPN?”
- Keep the answer. File the reply, the date and the name of the person who sent it with your vendor records. Our vendor claim checker helps you separate a specific answer from a vague one.
- Check your contract. Does it require the provider to tell you about a security incident affecting its tools, and how fast? If not, add it at renewal. Our guide on what belongs in a processor clause has wording to start from.
- Inventory remote-access tools on your own machines. List every remote-support app installed, who it belongs to and whether it is still needed. Remove what no one can explain.
What to watch next
- ConnectWise’s bulletins. Watch for updates on the RMM+ extension and the SCKit investigation.
- Provider notices. If your provider was affected, you may get a notice. Read it for dates, which machines were reachable and which credentials were rotated.
- Other tools your provider runs. CISA also issued an alert on November 17 urging organizations to patch a critical Java flaw, CVE-2026-114938, including copies of Java bundled inside other products. If your provider manages servers for you, it is a reasonable follow-up question.
Not sure whether your IT provider’s tools are affected, or what a good answer looks like? Our $49 Am I Affected? Check reads the advisories against what you tell us about your setup and replies within 1 business day with a plain answer and 3 to 5 steps, including what to ask your provider.
Sources
- ConnectWise, “ScreenConnect 26.6.5 Security Patch,” September 8, 2026, checked November 18, 2026 (CVE-2026-84869, CVSS 9.9, versions before 26.6.5 affected, servers not impacted, reinstall host clients, TransferFiles mitigation)
- Huntress, “CVE-2026-84869 in ScreenConnect Exploited to Run Malicious Files on MSP Technician Accounts,” John Hammond, November 16, 2026 (in-the-wild exploitation, 688,000 requests across 42 servers, client versions, recommendations)
- Microsoft Security Blog, “SCKit abuses ScreenConnect to deploy remote access and target technician sessions,” November 13, 2026 (RMM+ extension flaw per ConnectWise, mitigation guidance)
- CISA Known Exploited Vulnerabilities catalog, catalog version 2026.11.17, checked November 18, 2026 (CVE-2026-84869 added September 11, due September 14, forensic triage Yes)
- CISA, “Critical Java Vulnerability Requires Immediate Patching,” November 17, 2026 (CVE-2026-114938)
Related: N-able N-central and your IT provider, the BeyondTrust remote support zero-day, SonicWall SSL VPN and SAML, and Security and vulnerabilities.
Follow Circuit & Capital on Bluesky, Facebook and X (@circuitsfit) for new briefings.
