# CVE-2026-131610: In ConnectWise Automate versions prior to 2026.11, a condition in Web Control Center (WCC2) authorization handling could allow an authentica


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-hg44-5w94-729v

## What is CVE-2026-131610?

CVE-2026-131610 is a medium-severity vulnerability in ConnectWise Automate, published on 19 Nov 2026. 

### Official 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-131610?


## How do I fix CVE-2026-131610?

Upgrade ConnectWise Automate to 2026.11 or later. The advisory says that version fixes it.

## Is CVE-2026-131610 being exploited?

There is no known exploitation of CVE-2026-131610 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-131610 and fix it if it is affected.

What it is: CVE-2026-131610 is a medium-severity vulnerability in ConnectWise Automate, published on 19 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-131610 in the wild and no public exploit code.

Affected product: ConnectWise Automate. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-131610/ (Markdown: https://insights.sbomify.com/CVE-2026-131610/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-131610
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-131610
- OSV: https://osv.dev/vulnerability/CVE-2026-131610

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-131610/
Summaries are generated and may contain mistakes; the official description above is the record.
