CVE
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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.38% · 32nd percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 40/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
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.
Read the original 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.
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.
cve.now Index
- Exploitation0/40No signal
- Exposure25/25Default setups, CISA rates it automatable
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.3, total technical impact per CISA
- No patch5/5No patch listed yet
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
What to do
Check every install: default setups are affected.
Workaround: Disable the RMM+ extension immediately and verify that it remains disabled.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- CVE published
- First seen by cve.now
- Posted on X by cve.now1 day
- Record last updated
Affected versions
- DataComm RMM+
Version range not reported
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-127063
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: cve.now feed data
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: github.com
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: github.com
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: github.com
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: github.com