ScreenConnect Investigation Complete, but On-Premises Attacks Continue

ConnectWise says its investigation is complete, but continued activity targets unpatched on-premises ScreenConnect systems with five extensions enabled. Verify every technician client is 26.6.5 or later; patching does not remove established persistence.

Reader ratingRate this article

Loading reader rating…

Privacy-conscious voting uses a signed random browser identifier and a short-lived network hash; the rating tables contain no raw IP-address column.

Reader ratings require JavaScript; the article remains fully readable without it.

Bottom line: ConnectWise says its investigation is complete, but researchers continue to report activity against on-premises environments where the five identified extensions remain enabled and ScreenConnect has not been updated.[1]

Reporting cutoff: November 17, 2026 at 2:12:14 a.m. EST / 07:12:14 UTC. ConnectWise labels its latest update November 16, 2026 at 20:00 UTC and the investigation complete.[1]

Vendor statusInvestigation complete; partner action remains required.[1]
Client minimumEvery technician client must run ScreenConnect 26.6.5 or later; updating the server alone does not confirm client updates.[1]
Eradication boundaryDisabling extensions and updating software do not remove unauthorized access or persistence already established on affected devices.[1]

What changed

ConnectWise says completion of its investigation does not establish that individual partner or customer environments are unaffected.[1]

The extensions that must remain disabled are Labtech Plus, RMM Plus, RMM+, RMM Plus Password Link, and RMM+ Password Link. On-premises partners must disable them themselves and must not re-enable or reinstall them pending further guidance.[1]

Continued campaign activity

Huntress reports a November 13 spike in detections related to this activity from new infrastructure, affecting an additional 205 hosts across 41 organizations.[2]

Huntress continues to associate observed access with RMM+ 1.0.31 and 1.0.32 when an administrator had never configured the extension access key and a blank key was accepted.[2]

Actions for ScreenConnect partners

  1. Contain the exposed path. On-premises partners must keep all five identified extensions disabled, update ScreenConnect to the latest supported version, and verify every technician client is 26.6.5 or later.[1]
  2. Do not equate patching with eradication. ConnectWise advises reviewing activity, invalidating active sessions, and assessing suspected compromise through separate security tooling.[1]
  3. Established persistence remains a separate problem. Disabling extensions and updating software do not remove unauthorized access or persistence already established on affected devices.[1]

CVE-2026-84869 boundary

ConnectWise classifies CVE-2026-84869 as CWE-862 Missing Authorization. The client-side condition may permit file transfer and execution through an active remote session without authorization or Host confirmation in certain circumstances; ScreenConnect servers are not impacted by that bulletin.[3]

ConnectWise assigns CVE-2026-84869 a CVSS 3.1 base score of 9.9 and identifies ScreenConnect 26.6.5 as the security update.[3]

What remains unknown

  • ConnectWise says completion of its investigation does not establish that individual partner or customer environments are unaffected.[1]

Open the live ConnectWise advisory[1]

Sources

  1. ConnectWise Trust Center — ScreenConnect advisory
  2. Huntress — SCKit and RMM+ investigation
  3. ConnectWise — ScreenConnect 26.6.5 Security Patch