dbcve.org
AutomateApplication · Connectwise

CVE-2025-11492

HIGH · 7.5 CVSS v3.1 Published 2025-10-16
Fix available
A fix is available. Upgrade to 2025.9 or later.
See remediation →
80/100
Remediation priority · High
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

ConnectWise Automate Agent allowed communications to be configured using unencrypted HTTP instead of HTTPS, enabling an on-path attacker with man-in-the-middle network positioning to intercept, modify, or replay agent-server traffic. The Automate 2025.9 patch updates the obfuscation method and enforces HTTPS for all agent communications.

MitigationUpgrade ConnectWise Automate to version 2025.9 or later to enforce HTTPS for all agent-server communications and eliminate the HTTP fallback vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AutomateApplication
Affected:< 2025.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Automate version
    Locate the installed ConnectWise Automate version number in the software or its configuration and compare it to the 2025.9 release. This is typically visible in the Automate dashboard, in the installer, or in the program's About section.
    Affected if The installed version is any version prior to 2025.9 (e.g., 2025.8, 2024.x, etc.)
  2. Identify agent communication configuration
    Locate the configuration file or setting that controls how the Automate Agent communicates with the server. Look for parameters that specify the protocol (HTTP/HTTPS), hostname, or port for agent-server traffic.
    Affected if A configuration option exists that specifies or allows HTTP (instead of requiring HTTPS) for agent-server communication.
  3. Verify if HTTP fallback is enabled
    Inspect the agent communication settings to determine whether the system is configured to allow or prefer unencrypted HTTP connections to the server.
    Affected if The configuration explicitly allows HTTP or contains an HTTP URL/port rather than requiring HTTPS for agent communications.

You are affected if your ConnectWise Automate installation is any version before 2025.9 AND the agent is configured to allow unencrypted HTTP communication with the server.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2025.9 or later
Fixed in 2025.9
Interim mitigation

Upgrade ConnectWise Automate to version 2025.9 or later to enforce HTTPS for all agent-server communications and eliminate the HTTP fallback vulnerability.

Recommended fix High confidence

Automate 2025.9

  1. 1. Identify the current version of ConnectWise Automate Agent by checking the agent system or management console
  2. 2. Obtain the Automate 2025.9 or later version from the official ConnectWise download portal or patch management system
  3. 3. Plan the upgrade during a maintenance window to minimize disruption
  4. 4. Run the upgrade installer or push the update through the Automate management system
  5. 5. After upgrade, verify that all agent communications are now enforced over HTTPS
  6. 6. Confirm the new version is displayed as 2025.9 or higher in the agent or server console
Caveat Version 2025.9 enforces HTTPS for all agent communications; any legacy systems relying on HTTP-only connections will need to be reconfigured

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Automate Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11492 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11492 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data