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.
Metrics
Affected Vendors & Products
Advisories
No advisories yet.
Fixes
Solution
Cloud: Cloud instances have already been updated to the latest Automate release. On-premise: Apply the 2025.9 release.
Workaround
No workaround given by the vendor.
References
History
Mon, 20 Oct 2025 13:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
First Time appeared |
Connectwise
Connectwise automate |
|
Vendors & Products |
Connectwise
Connectwise automate |
Thu, 16 Oct 2025 19:15:00 +0000
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
|

Status: PUBLISHED
Assigner: ConnectWise
Published:
Updated: 2025-10-17T03:55:31.431Z
Reserved: 2025-10-08T11:25:59.180Z
Link: CVE-2025-11492

No data.

Status : Received
Published: 2025-10-16T19:15:31.900
Modified: 2025-10-16T19:15:31.900
Link: CVE-2025-11492

No data.

Updated: 2025-10-20T13:24:54Z