ScreenConnect Vulnerability CVE-2026-84869: Exploited Flaw Runs on Technician Machines, Why Server Updates Fall Short, and Version 26.6.5
A ScreenConnect flaw, CVE-2026-84869, is being exploited, and the vulnerable code runs on the technician's machine. Updating the server is not enough: every technician install needs version 26.6.5.
Where Worldwide
On this page 8 sections
A flaw in ConnectWise ScreenConnect, the remote support tool that IT teams and providers use to reach the computers they look after, is being exploited by attackers. The catch is that the vulnerable code runs on the technician's machine. A team that only updated its ScreenConnect server may still be exposed, and so may every business it supports.
The flaw is tracked as CVE-2026-84869. ConnectWise published its security bulletin on Tuesday, September 8, 2026. The US Cybersecurity and Infrastructure Security Agency (CISA) added the flaw to its Known Exploited Vulnerabilities catalog on Friday, September 11, 2026. The fix is ScreenConnect version 26.6.5. Two months later, the useful question is not whether the server was patched. It is whether every technician's copy was.
What happened with the ScreenConnect vulnerability
ConnectWise's bulletin is short. It says: "ScreenConnect version prior to 26.6.5 are impacted." It also says: "ScreenConnect servers are not impacted." Its instruction is: "Please upgrade to ScreenConnect version 26.6.5."
Huntress, the security firm that wrote up the exploitation, explains why that split matters: "Updating the server alone doesn't fix this, because the vulnerable code runs on the technician's machine."
Huntress also describes how the attackers are behaving: "Attackers appear to be spraying servers blindly." Put simply, the attackers do not appear to be choosing their victims one by one. Huntress's report cites a figure of 70,414 requests.
ConnectWise rates the flaw with the CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. In plain terms, that string describes an attack that:
- works over the network
- is not complex to carry out
- needs only a low-level account
- needs nobody to click anything
- can affect things beyond the vulnerable component itself
- has a high impact on confidentiality, integrity and availability
What is confirmed and what is not
Confirmed by the primary sources:
- The flaw is CVE-2026-84869. CISA lists it as known exploited, with a date added of 2026-09-11.
- ScreenConnect versions before 26.6.5 are impacted, and 26.6.5 is the fixed version.
- ScreenConnect servers are not impacted. The vulnerable code is on the technician's machine.
- Huntress reports that attackers appear to be hitting servers widely rather than picking targets.
Not known from the sources we checked:
- How many IT providers or businesses have actually been compromised. Some reports about this campaign give much larger figures than the one above. We could not match them to a primary source, so we are not repeating them.
- Over what period, or across how many servers, Huntress counted its 70,414 requests.
- Exactly how requests sent to servers reach a technician's machine. The sources we used do not explain that in a way we can repeat with confidence.
- What a search for TransferFiles in your own records would prove. Huntress's write-up names TransferFiles in its account of the activity, but our sources do not explain its role well enough for us to tell you what a match means.
If your provider tells you something specific that goes beyond this list, ask where it came from.
Why updating the ScreenConnect server is not enough
The server is usually the part of a remote access tool that people think to patch. It sits in one place, it shows up in scans, and updating it feels like the job is done. This flaw does not work that way. ConnectWise says the servers are not impacted, and Huntress says the vulnerable code runs on the technician's machine.
So a provider can have an up-to-date server while its technicians work from laptops running a vulnerable version. We wrote about the same trap in a different product in Updated Is Not the Same as Patched: the version number on the thing you checked does not prove that the thing that matters is fixed.
Who needs to act
- IT providers (MSPs) that use ScreenConnect. The fix has to land on your technicians' computers.
- In-house IT teams that use ScreenConnect to support staff or remote offices. The same rule applies: every technician install, not just the server.
- Businesses whose IT provider uses ScreenConnect. You may never have installed it yourself, but your provider's technicians use it to reach your computers. You are entitled to ask whether they have moved to 26.6.5.
What to do this week
| Step | What to check | Done when |
|---|---|---|
| 1. List every technician install | Every computer that runs ScreenConnect as a technician, including laptops used from home | You have a complete list with an owner for each machine |
| 2. Check the version on each | The ScreenConnect version on each technician machine | Every machine shows 26.6.5 |
| 3. Upgrade anything older | Any technician install before 26.6.5 | Upgraded to 26.6.5, as ConnectWise's bulletin instructs |
| 4. Do not stop at the server | Whether the update went only to the server | The technician machines are confirmed, not assumed |
| 5. Get it in writing from your provider | Whether their technician machines run 26.6.5, and since when | You have a written answer with a date |
| 6. Review recent activity | Ask whoever reviews your remote access logs to read the Huntress report, including its references to TransferFiles | Someone qualified has looked and written down what they found |
If nobody in your business would know who to ask in step 5, fix that too. Who Is Patching the Software That Runs Your Business? covers how to pin it down.
Why it matters for a business network
A remote support tool is one of the most trusted paths into a company network. It exists so that someone outside the building can work on your computers. When the weak point is the technician's own computer, the risk does not stop at that one machine. Whoever gets control of it may be able to reach whatever that technician can reach.
For an IT provider, that could mean many customers at once. For a business, it means your security depends partly on the patching habits of people you may never meet. That is not a reason to panic or to drop your provider. It is a reason to ask a direct question and expect a direct answer.
If you run your own servers and remote access, our self-hosting and infrastructure work is built around knowing exactly what runs where and who keeps it updated.
ScreenConnect vulnerability questions people are asking
Is CVE-2026-84869 being exploited?
Yes. CISA lists it in its Known Exploited Vulnerabilities catalog with a date added of 2026-09-11, and Huntress has written up attacks that use it.
Which ScreenConnect versions are affected?
ConnectWise says ScreenConnect versions prior to 26.6.5 are impacted.
What version fixes the ScreenConnect vulnerability?
ScreenConnect 26.6.5. ConnectWise's instruction is to upgrade to that version.
Are ScreenConnect servers affected by CVE-2026-84869?
ConnectWise says ScreenConnect servers are not impacted. The vulnerable code runs on the technician's machine, which is why updating the server alone does not fix it.
How serious is CVE-2026-84869?
ConnectWise gives it the CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. That describes a network attack that needs only a low-level account and no user action, with high impact.
My IT company uses ScreenConnect. What should I ask them?
Ask three things: whether every technician machine runs ScreenConnect 26.6.5, when they upgraded, and whether they have checked their activity against the Huntress report.
How many companies were hacked through ScreenConnect?
That is not confirmed. Huntress cites 70,414 requests, but we have no primary-source count of compromised providers or businesses.
The bigger lesson
Patch where the vulnerable code runs, not where it is easiest to check. For ScreenConnect, that means every technician's computer, not only the server.
Want your remote access and servers checked properly? See security hardening or get a quote.
Get security alerts like this by email, with our free checklist, at /security-alerts.
Sources: ConnectWise ScreenConnect security bulletin; CISA Known Exploited Vulnerabilities Catalog; Huntress.
Have a question about this article?
Ask it here and we will answer you directly by email. Questions are private, never posted.
Security alerts by email
Hear about the next one first.
When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.
Want a result like this?
Security alerts, breaches and the technology a business runs on: what happened, who it affects and what to do.
Get a Tech QuoteKeep reading
Microsoft 365 Outage Phishing: Fake Held-Mail Emails Used the November 12 Disruption as Bait, What Is Confirmed and How to Check Who Clicked
Phishing emails used the November 12 Microsoft 365 outage as cover, falsely claiming messages held during the...
Fireworks AI Data Breach: Uber Notifies 149,346 People After Hackers Stole Driver License Data From Its AI Vendor, What Is Confirmed and What Businesses Should Check
Uber says hackers stole drivers' names, addresses, dates of birth and license numbers in a breach at vendor Fi...
PostgreSQL Security Update: 52 Vulnerabilities Fixed Including CVE-2026-6460, PostgreSQL 14 Reaches End of Life, and the Versions to Install
PostgreSQL's November 12 update fixes 52 security vulnerabilities, including CVE-2026-6460, a code execution f...