ConnectWise Directs On-Premises Customers to Disable the DataComm RMM+ Extension
Tech GuruQuick Answer
Disable the RMM+ extension immediately on premises and verify it stays disabled. Do not reinstall or re-enable it pending guidance; ConnectWise reports cloud removal is complete.
Confirm Scope And Apply The Supported Remediation
What to do now: Identify RMM+ installations, hosting model, configured API secret, managed-agent scope and administrators responsible for extensions. Limit this assessment to the third-party RMM+ extension. Do not label the ScreenConnect server or client itself vulnerable to this issue. Follow ConnectWise’s disablement instruction. A changed secret is not a substitute for the published instruction to keep the extension disabled pending guidance. Verify extension state and review extension requests and commands sent to agents. Preserve configuration, command histories, administrative changes and endpoint evidence; investigate unexpected activity.
Last verified: 2026-11-13 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Third-party DataComm RMM+ extension for ConnectWise ScreenConnect |
|---|---|
| Advisory | CVE-2026-127063 |
| CVE | CVE-2026-127063 |
| Authoritative release date | 2026-11-12 — November 12, 2026 at 17:47:34 UTC, when the advisory file was added to the ConnectWise disclosure repository; the advisory states November 12. |
| Authority revision date | No separate revision date is provided by the authority. |
| Affected versions | RMM+ deployments retaining the default static API secret. ConnectWise does not specify a numbered affected-version range. ScreenConnect server and client software and deployments without the extension are not affected by this issue. |
| Fixed version | No fixed RMM+ version is announced. Disable the extension on premises; ConnectWise says it disabled and removed affected extensions in cloud-hosted environments. |
| CVSS base score | 9.3 (CVSS v4.0 base score) |
| CVSS severity | Critical |
| Exploitation status | ConnectWise does not confirm exploitation in the wild in this disclosure.; no exploitation claim is inferred. |
What Changed
The default RMM+ API secret can permit unauthorized extension API access, including commands to managed agents. ConnectWise’s disclosure calls for disabling the third-party extension and distinguishes it from ScreenConnect server and client vulnerabilities.
What To Validate Now
- Inventory. Identify RMM+ installations, hosting model, configured API secret, managed-agent scope and administrators responsible for extensions.
- Establish applicability. Limit this assessment to the third-party RMM+ extension. Do not label the ScreenConnect server or client itself vulnerable to this issue.
- Remediate. Follow ConnectWise’s disablement instruction. A changed secret is not a substitute for the published instruction to keep the extension disabled pending guidance.
- Validate. Verify extension state and review extension requests and commands sent to agents. Preserve configuration, command histories, administrative changes and endpoint evidence; investigate unexpected activity.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Disabling the integration may interrupt automation. Coordinate dependent workflows and monitor for re-enablement. Do not present an unannounced extension upgrade as a fix.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
