cybersecurity
ConnectWise ScreenConnect Update Puts Third-Party Extensions in the Spotlight
Published: 13 November 2026 (IST) ConnectWise has updated its public ScreenConnect security advisory with a more detailed account of an ongoing investigation into unauthorized access reported in certain partner environments. The update matters because…
Published: 13 November 2026 (IST)
ConnectWise has updated its public ScreenConnect security advisory with a more detailed account of an ongoing investigation into unauthorized access reported in certain partner environments. The update matters because it shifts the technical focus away from a simple product-version story and toward the relationship between a remote-support platform, independently developed extensions, administrative access, and technician workstations.
In its Trust Center advisory, ConnectWise says it has found no evidence that ConnectWise infrastructure was compromised or that the initial access involved a ScreenConnect vulnerability. The company says its initial assessment suggests the activity may involve abuse of third-party extensions installed in partner environments, while stressing that the assessment remains under validation.
What changed in the latest update
The latest update, dated November 12, 2026 at 18:45 UTC, adds detail to an investigation that ConnectWise first described publicly on November 11. The company says it identified approximately 400 partner environments with at least one independently developed extension from the RMM+ family. Those extensions expose an API capable of executing remote commands and use a passphrase configured during setup.
ConnectWise is careful to distinguish presence from confirmed impact. An environment having one of the extensions installed does not, by itself, establish that unauthorized activity occurred. That distinction is important in incident reporting: an inventory count can describe exposure to a particular component without serving as a count of confirmed compromises.
The extensions named in the advisory include Labtech Plus, RMM Plus, RMM+, RMM Plus Password Link, and RMM+ Password Link. ConnectWise says it disabled the identified extensions in approximately 400 cloud environments as a precaution and advised on-premises partners to disable them themselves.
Where the ScreenConnect client fits
The advisory also discusses a separate ScreenConnect client fix. ConnectWise says version 26.6.5, released on September 8, 2026, blocks an endpoint-to-technician spread technique described in reports from third-party researchers. The company says the fix addresses that attempted spread technique, but does not establish how initial access occurred, prevent every form of unauthorized software deployment, or remove an existing compromise.
That is a subtle but useful distinction. A client update can close one route for movement or reduce the effect of a known technique, while leaving the original entry point and any independent extension behavior as separate questions. In a remote-management environment, administrators therefore have to understand which control addresses which stage of an event.
What researchers have reported
ConnectWise’s advisory separates its own findings from observations reported by third-party researchers. Those reports describe unauthorized ScreenConnect deployments and a toolkit called SCKit. The advisory says researchers reported that the toolkit was designed to spread from infected endpoints to connecting technician workstations and then to other accessible endpoints, while also noting that the reported spread technique had not been observed succeeding at the time of the update.
The advisory further says researchers reported an authentication flaw in RMM+ versions 1.0.31 and 1.0.32 that could accept an empty access key when none had been configured. ConnectWise says it is assessing those findings alongside its investigation. The wording matters: these are reported observations under review, not a final public determination about the full incident scope.
Why third-party extensions change the risk picture
Remote-support platforms are often most useful when they can be extended. An add-on may connect ticketing, automation, passwords, scripts, reporting, or device workflows that the core product does not provide. But an extension can also add a new identity boundary, a new configuration secret, a new update path, and a new capability that must be understood by the platform owner.
The ScreenConnect update illustrates why extension inventories need to be more than a list of names. An administrator may need to know which extension is installed, who maintains it, what permissions or APIs it exposes, how its secrets are configured, how it is updated, and whether its activity is visible in central logs. The operational question is not simply “Is this plugin approved?” but “What can it do, and how would we know if its behavior changed?”
What ConnectWise says partners should review
ConnectWise’s advisory lists several actions for partners, including verifying technician clients are on version 26.6.5 or later, keeping the named extensions disabled, reviewing file-transfer permissions, invalidating active sessions, and using separate security tooling for investigation and remediation. It also says partners should preserve relevant records, review authentication and administrative activity, and treat client updates or credential resets as different from investigating an existing compromise.
Those points are presented here as a summary of ConnectWise’s published guidance, not as an independent assessment or a recommendation about any particular organization. The advisory also notes that ConnectWise does not have visibility into activity inside partner environments after initial access, so it cannot independently determine what may have occurred there.
The operational lesson beyond this incident
The most transferable lesson is about layered responsibility. A cloud console, an endpoint client, a third-party extension, an identity provider, and a technician workstation can each sit on a different part of the same workflow. Updating one layer does not automatically validate the others.
For platform teams, this means incident readiness should include extension inventories, clear ownership for add-ons, logs that connect administrative activity to endpoints, and a way to work out-of-band if the remote-management tool itself is part of the investigation. These are design and operations questions that apply to many remote-access products, not just ScreenConnect.
What remains unresolved
ConnectWise says the initial access method, the full scope, and the relationship between the reported activity and the third-party extensions remain under investigation. It also says an absence of matching indicators does not rule out compromise. Further updates may therefore change the technical picture.
For now, the important change is clarity about boundaries. The advisory distinguishes ConnectWise infrastructure from partner environments, the ScreenConnect client from independent extensions, reported observations from confirmed findings, and containment measures from full remediation. Those distinctions make the update more useful than a simple “patch available” headline because they show where the remaining uncertainty actually sits.
This article is a general information summary based on the cited public sources. It is not legal, cybersecurity, or compliance advice.