ScreenConnect CVE-2026-84869: What Texas SMBs Should Ask Their MSP

A critical ScreenConnect flaw is being exploited against MSP technicians. Here is what the remote access security threat means for your business and what to ask your MSP now.
Introduction
A critical ScreenConnect vulnerability is being used to break into the computers of the people who manage your IT. Tracked as CVE-2026-84869, the flaw lets a malicious "guest" in a remote support session push a file to the technician's machine and run it, without the technician approving anything. Security researchers at Huntress documented real compromises of MSP technicians on November 12 and 13, 2026. For a Texas SMB, the stakes are direct: if your managed service provider's technician workstation is compromised, an attacker may inherit the saved credentials and remote access that reach into your network. Here is what happened, what to ask your provider this week, and how to limit the blast radius.
What CVE-2026-84869 Actually Does
ConnectWise disclosed the flaw on September 8, 2026, and CISA added it to its Known Exploited Vulnerabilities catalog three days later. According to public reporting on Huntress's research, the bug sits in how ScreenConnect host clients (the software the technician runs) handle guest file transfers during Support and Access sessions.
- Severity: rated CVSS 9.9.
- Trigger: the technician only has to join a session. A malicious guest can send a file and have it execute, potentially with elevated rights.
- Who is targeted: MSP technicians, whose workstations typically hold credential vaults, RMM consoles, and admin access to many customers at once.
- Scale: reporting describes very large volumes of malicious guest requests to run batch files across dozens of MSP-hosted ScreenConnect servers between late October and mid-November. Most were delivery attempts rather than confirmed infections, but the campaign is active.
This is the same pattern we covered with the BeyondTrust Remote Support zero-day: attackers go after remote support tools because one compromise unlocks many businesses.
Why Patching the Server Is Not Enough
The detail that catches teams out is that this is a client-side problem. Updating the ScreenConnect server does not fix the technician workstations. The guidance relayed from ConnectWise and Huntress is:
- Update every technician's host client to version 26.6.5 or later, along with any affected Access agents.
- If a client cannot be patched right away, remove the TransferFiles permission from roles and session groups until it can.
- Hunt for guest-originated file transfers and executions, especially ones that line up with a technician being connected.
- On any confirmed compromise: isolate the workstation, remove unauthorized remote access clients, and rotate every management, vault, and customer admin credential that machine could reach.
If you run ScreenConnect in-house rather than through a provider, the same steps apply to your own IT staff. Treat the KEV listing as your deadline, a principle we explain in our guide to EPSS vulnerability prioritization.
Five Questions to Ask Your MSP This Week
You do not need to read ScreenConnect logs yourself. You do need clear answers from whoever manages your IT. Send these in writing:
- Do you use ScreenConnect, directly or inside another RMM platform, to access our systems?
- Are all technician host clients on 26.6.5 or later, and on what date was that confirmed?
- Have you reviewed session logs for guest-initiated file transfers since October, and did you find anything tied to our environment?
- Which of our credentials live on technician workstations, and would you rotate them if a technician machine were compromised?
- How will you notify us if an incident at your company touches our data, and how fast?
A good provider will answer quickly and specifically. Vague answers are a finding in their own right. Our MSP vendor security questionnaire and checklist of MSP contract clauses to check help you formalize this beyond a single incident.
Limit What a Compromised Provider Can Reach
Every SMB that uses outside IT support carries some third-party risk. The goal is to make sure one compromised technician cannot quietly own your whole environment:
- No standing domain admin for vendors. Use just-in-time elevation through privileged access management so access expires.
- Require MFA and named accounts for every provider login. Shared "msp-admin" accounts make investigation nearly impossible.
- Inventory every remote access tool on your devices and remove the ones nobody can justify. Our secure remote access guide for Texas SMBs covers safer options.
- Alert on new remote access installs through your EDR so an unknown agent is caught within hours, not weeks.
- Keep offline or immutable backups that a compromised admin account cannot delete, as outlined in our 3-2-1-1-0 immutable backup guide.
For a broader framework, see our article on third-party vendor risk management for Texas SMBs.
Warning Signs to Watch For
Because this flaw was exploited in the wild, check for signs of activity rather than assuming you are clean:
- Remote access software you did not authorize, or a second copy of a tool you already use.
- New local administrator accounts or unexpected changes to security software settings.
- Admin sign-ins at unusual hours or from unfamiliar locations, especially from provider accounts.
- Scheduled tasks or MSI installers named to look like Windows updates.
If you see any of these, follow the containment steps in our remote access compromise remediation guide and loop in counsel early if client or patient data could be involved.
Where to Start
Today, email your IT provider the five questions above and ask for written answers by the end of the week. In parallel, pull a list of every remote access tool installed on your devices and confirm each one has an owner and a business reason. If you want a second set of eyes, our cybersecurity services team can run a remote access exposure review, and our managed IT services are built on named accounts, MFA, and time-limited admin access. To see how your controls compare with peers, review the Texas SMB IT and cybersecurity benchmark.
Geographic Coverage
Want us to fix it for you?
The steps above work if you know exactly which machines run the affected software. Most offices don't, and that's where a patch for CVE-2026-84869 gets missed: the old server in the closet, the laptop that never reboots, the appliance nobody has logged into since it was installed.
We can find every copy, apply the vendor's update or its workaround, and show you the check that proves it took. If you think you've already been hit, say so when you call and we'll start with containment.
20+ Years Experience · 100% U.S.-Based Support · Business hours, plus after-hours emergency support
Tracking how CVE-2026-84869 develops? Latest news and timeline on CVERadar
Need Help With Cybersecurity?
LayerLogix provides expert cybersecurity solutions for businesses across Houston and nationwide.
Related Articles
Need Expert IT Support?
Let our team help your Houston business with enterprise-grade IT services and cybersecurity solutions.


