HTTP Configuration and Encryption in Transit
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| ConnectWise | Automate | unaffected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Connectwise | Automate | — |
Vendor Solution
Cloud: Cloud instances have already been updated to the latest Automate release. On-premise: Apply the 2025.9 release.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.203% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:connectwise:automate:*:*:*:*:*:*:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Connectwise
Connectwise automate |
|
| Vendors & Products |
Connectwise
Connectwise automate |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In the ConnectWise Automate Agent, communications could be configured to use HTTP instead of HTTPS. In such cases, an on-path threat actor with a man-in-the-middle network position could intercept, modify, or replay agent-server traffic. Additionally, the encryption method used to obfuscate some communications over the HTTP channel is updated in the Automate 2025.9 patch to enforce HTTPS for all agent communications. | |
| Title | HTTP Configuration and Encryption in Transit | |
| Weaknesses | CWE-319 | |
| References |
| |
| Metrics |
cvssV3_1
|