CVE-2026-127063

waiting for further signalsZero needs more public information before it can validate it.

GHSA-h94v-vx95-5jpx ↗EUVD-2026-124597 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
DataComm RMM+ All extension versions
CWE-1392 Use of Default Credentials
ETK-2026-4299Zero's internal tracking ID, independent of the CVE number., permanent identifier
8h 49msince last run
16mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h19m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

The third-party DataComm RMM+ extension for ConnectWise ScreenConnect is affected when its API secret remains set to the default value. A party able to use that default may access extension API functions and issue commands to managed agents; ScreenConnect server and client software are not affected.

mitigation

Replace the RMM+ default API secret with a unique administrator-controlled value immediately. Restrict access to the extension API and verify that no deployment retains the default secret.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
16m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-12 17:50Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-12 17:50Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-127063

{
  "etk_id": "ETK-2026-4299",
  "cve_id": "CVE-2026-127063",
  "display_id": "CVE-2026-127063",
  "ghsa_id": "GHSA-h94v-vx95-5jpx",
  "euvd_id": "EUVD-2026-124597",
  "status": "triaged_in_scope",
  "anchor_state": "anchored",
  "title": "Default API secret in DataComm RMM+",
  "summary": "The third-party DataComm RMM+ extension for ConnectWise ScreenConnect is affected when its API secret remains set to the default value. A party able to use that default may access extension API functions and issue commands to managed agents; ScreenConnect server and client software are not affected.",
  "mitigation": "Replace the RMM+ default API secret with a unique administrator-controlled value immediately. Restrict access to the extension API and verify that no deployment retains the default secret.",
  "vendor": "DataComm",
  "product": "RMM+",
  "affected": [
    {
      "affected_notes": [
        "All extension versions"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "RMM+",
      "purl": null
    }
  ],
  "cwes": [
    1392
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_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",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 16.031751566666667,
  "t0_at": "2026-11-12T17:50:07.196000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-12T17:50:07.196000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-12T17:50:07.196000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-127063"
    }
  }
}

published 2026-11-12 18:13Z
last change 2026-11-12 23:56Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.