CVE-2026-84869 in ScreenConnect Exploited to Run Malicious Files on MSP Technician Accounts
Source AlienVault OTX General
Exploited in the wild · KEV due 14 Sep 2026 : block it and hunt for it in your logs now.
Data as of 17 Nov 2026, 10:19 UTC
- KEV deadline
- US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 8 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 3 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
CVE ID reserved
by ConnectWise LLC
, 6 days before disclosure
CVE published
on cve.org
, t = 0
In Threat Radar
record ingested
, 8 minutes after disclosure
Added to CISA KEV (opens in a new tab)
exploitation confirmed
, 3 days after disclosure
KEV remediation due
US federal deadline
, 6 days after disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ConnectWiseScreenConnect | Affected
| Fixed in– |
Description
A critical vulnerability in ConnectWise ScreenConnect (CVE-2026-84869, CVSS 9.9) allows malicious guests in remote sessions to push files to technician workstations and execute them with elevated privileges without authorization. Between October and November 2026, attackers conducted a massive spray campaign across 42 MSP ScreenConnect servers, issuing 688,000 malicious file-transfer requests. One successful exploitation achieved full compromise in nine seconds, deploying a rogue ScreenConnect client branded as Windows Update and connected to attacker infrastructure at masterdarky[.]com. Attack techniques included worm-like propagation, path traversal to inject startup scripts, and strategic targeting of MSP technician workstations that hold RMM consoles and customer credentials. Additional campaigns planted unauthorized crypto-exchange-named guest sessions as lures, while test runs used canary files to verify exploitation success before deploying actual payloads.
Indicators of compromise
Domains 1
- masterdarky.com
URLs 1
- https://masterdarky.com/WindowsUpdate.msi
IP addresses 11
- 194.15.36.33
- 38.18.228.173
- 172.81.61.149
- 38.18.228.165
- 154.30.4.248
- 178.173.246.85
- 181.215.242.106
- 38.18.229.249
- 50.114.203.14
- 66.118.239.23
Hashes 1
CVEs 1
- CVE-2026-84869