ConnectWise Automate authorization flaw in WCC2 exposes other clients' data
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
ConnectWise Automate versions before 2026.11 have a flaw in how Web Control Center (WCC2) checks authorization. A user with a low-privilege contact account can reach the server over the network through API requests and view information belonging to other clients on the same Automate server.
Written by a model
Original description
In ConnectWise Automate versions prior to 2026.11, a condition in Web Control Center (WCC2) authorization handling could allow an authenticated contact user to access information associated with other clients on the same Automate server through API requests. This may result in disclosure of information outside the user’s assigned access scope. The issue is limited to information disclosure and does not extend existing modification or command execution permissions. This issue is resolved in ConnectWise Automate 2026.11.
What to do
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-131610 (In ConnectWise Automate versions prior to 2026.11, a condition in Web Control Center (WCC2) authorization handling could allow an…), 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-131610 (entry last updated 2026-11-19):
Affected:
- ConnectWise Automate: versions All versions prior to 2026.11
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-131610 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131610 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-131610
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-131610
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-131610"}.Affected versions
- ConnectWise AutomateAll versions prior to 2026.11
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.5/10CVSS 6.5
- No patch5/5No patch listed yet
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131610 |
| Record | NVD · CVE-2026-131610 |
| Other links 1 | |
| Repository | GitHub · ConnectWise-Advisories/Disclosures · tree/main/CVE-2026-131610 |
Questions about CVE-2026-131610
Is CVE-2026-131610 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
Which versions are affected by CVE-2026-131610?
Automate: version All versions prior to 2026.11.
Source: cve.now feed data
Related
- CVE-2025-11492HTTP Configuration and Encryption in Transit
- CVE-2026-9089The ConnectWise Automate™ Agent does not fully verify the authenticity of components obtained during plugin loading and self-update operatio
- CVE-2025-11493Self-Update Verification Mechanism Process in ConnectWise Automate
- CVE-2026-6066Unencrypted Client‑Server Communication in ConnectWise Automate™ Solution Center
- CVE-2024-1709Authentication bypass using an alternate path or channel
- CVE-2026-84869ScreenConnect Client: Guest-to-Host File Execution via File-Transfer Actions
No corrections so far. Something wrong on this page? Report an error.