ScreenConnect vulnerabilities and CVEs

Every ConnectWise ScreenConnect CVE that CISA lists as exploited, with the fixed versions, scores and dates from ConnectWise, CISA and NVD. Use it to check your server and clients.

See the CVE table
By CalMax Systems Security Research · Published November 18, 2026 · Last updated: November 18, 2026 · Checked against ConnectWise, CISA and NVD (sources below)

How many ScreenConnect CVEs are exploited?

CISA’s Known Exploited Vulnerabilities catalog lists four ScreenConnect CVEs: CVE-2026-84869, CVE-2025-3935, CVE-2024-1708 and CVE-2024-1709. What to do: upgrade on-premises servers to the latest supported release, then reinstall host clients and update access agents. Cloud or on-premises, check that every technician’s ScreenConnect client runs 26.6.5 or later, as ConnectWise’s November 16, 2026 advisory requires. ConnectWise has already updated its cloud servers. Patching does not remove an attacker who is already in.

Looking for the November 2026 attacks? In its November 12 update, ConnectWise said it had found no evidence that initial access involved a ScreenConnect vulnerability; its initial assessment pointed to abuse of third-party RMM+ extensions. It verified that client 26.6.5 and later block the endpoint-to-technician spread technique used by the attackers’ toolkit, SCKit. Steps and checks are in ScreenConnect attacks, November 2026: what to do now.

ScreenConnect CVEs in CISA’s exploited list

Newest disclosed first. Checked against the CISA KEV catalog of November 18, 2026, the NVD records and the ConnectWise bulletins.

CVE What it is Affected / fixed CVSS Added to CISA KEV Known ransomware use
CVE-2026-84869 Client flaw: files can be transferred and run through an active session without authorization or Host confirmation, in certain circumstances. Servers are not impacted. Clients before 26.6.5 / fixed in 26.6.5 (NVD build cutoff: 26.6.5.9742) 9.9 (ConnectWise, CVSS 3.1) September 11, 2026 Unknown
CVE-2025-3935 ViewState code injection on the server. Only possible if the attacker already has the server’s machine keys. 25.2.3 and earlier / fixed in 25.2.4 (patches also for some older versions back to 23.9) 7.2 (NVD), 8.1 (ConnectWise), CVSS 3.1 June 2, 2025 Unknown
CVE-2024-1708 Path traversal on the server, which may allow remote code execution. 23.9.7 and prior / fixed in 23.9.8 (see the 22.4 note below) 8.4 (NVD, CVSS 3.1) April 28, 2026 Known
CVE-2024-1709 Authentication bypass: an attacker with network access to the management interface can create a new administrator-level account. 23.9.7 and prior / fixed in 23.9.8 and in interim build 22.4.20001.8817 10.0 (NVD, CVSS 3.1) February 22, 2024 Known
Not in CISA’s list: CVE-2026-3564 (March 17, 2026; CVSS 3.1 score 9.0 from ConnectWise) affects ScreenConnect servers before 26.1. Earlier versions stored server machine keys in configuration files, and under certain conditions that material could be extracted and misused for session authentication. ConnectWise says cloud instances need no action for this CVE. On-premises partners should upgrade to the latest supported release, with 26.1 as the minimum fix. ConnectWise’s March 17 authentication hardening advisory says 26.1 also lets administrators regenerate the instance’s cryptographic material on demand; if you suspect the keys were exposed, investigate for unauthorized access and regenerate them.

CVE-2026-127063, published November 12, 2026, is a static default API secret in the third-party RMM+ extension (CVSS 4.0 score 9.3 from ConnectWise). The CVE record lists every RMM+ version as affected: deployments that keep the default secret may allow unauthorized access to the extension’s API. ConnectWise says it does not affect the ScreenConnect server or client, and no fixed RMM+ version has been announced. ConnectWise has disabled these extensions in its cloud environments. On-premises partners must immediately disable Labtech Plus, RMM Plus, RMM+, RMM Plus Password Link and RMM+ Password Link. ConnectWise advises all partners with these extensions, including cloud partners, to verify that they remain disabled across their instances and to keep them disabled or uninstalled pending further guidance. As a precaution, ConnectWise disabled ITBoost Integration, RepairShopr Integration and Guest Session Starter in its cloud. It urges partners to disable any of these extensions that are still enabled and keep them disabled until further notice. On-premises partners must take this action themselves. The campaign is covered in our November 2026 guide.

How to check your ScreenConnect version

The server check applies to on-premises servers. ConnectWise updates its own cloud servers. Technician clients need checking on both.

  1. Sign in to your ScreenConnect server as an administrator.
  2. Go to Administration > Overview to see your current version and the version your license can install. ConnectWise’s 26.6.5 bulletin points here. Older bulletins point to Administration > License > Version Check.
  3. Compare your version with the table above. A server on 26.6.5 or later is at or above every fixed version in the table.
  4. CVE-2026-84869 is a client flaw. After the server upgrade, reinstall your host clients and update your access agents. Then check the client version on every technician workstation, including technicians who use ScreenConnect Cloud.

If your license is out of maintenance, check Latest Eligible Version on Administration > Overview first: ConnectWise says partners whose renewal is due in 2026 can upgrade to 26.6 without renewing. Otherwise, ConnectWise says to upgrade your license before installing the latest release. ConnectWise says on-premises servers must already run 25.4 or later to upgrade to 26.6.5, so older servers need to upgrade in steps. Follow the upgrade path in the bulletin for your version. If your path includes the 25.2.4 upgrade, its bulletin says to update access agents after each incremental upgrade. For on-premises ScreenConnect integrated with Automate, ConnectWise supplies 26.6.5 through Automate Product Updates for partners with active Automate Assurance.

CVE-2026-84869: client file transfer flaw

A condition in the ScreenConnect client may allow files to be transferred and executed through an active remote session without authorization or Host confirmation, in certain circumstances. ConnectWise says ScreenConnect servers are not impacted. ConnectWise rates it 9.9 (CVSS 3.1). CISA added it to its exploited list on September 11, 2026.

  • Affected: ScreenConnect clients before 26.6.5.
  • Fixed: ScreenConnect 26.6.5 and later (bulletin of September 8, 2026).
  • Cloud: ConnectWise has updated its cloud servers to 26.6.5. Cloud partners still need to reinstall host clients, update access agents and check that every technician workstation runs client 26.6.5 or later. ConnectWise’s November 16, 2026 advisory says updating the server or cloud console alone does not confirm that technician clients are updated.
  • On-premises: upgrade the server to 26.6.5 or later, then reinstall your host clients and update your access agents.
  • If you can’t patch yet: ConnectWise says you can remove the TransferFiles permission (called TransferFilesInSession in older versions) from each role’s session groups under Administration > Security > Roles. It warns this is not a substitute for the update.

How to check if you’re affected: check the ScreenConnect client version on every technician workstation. Each must run 26.6.5 or later, cloud or on-premises. A server upgrade alone is not the whole fix. After patching, ConnectWise says to review users, roles and permissions, remove users you don’t recognize, change passwords and enable MFA.

It is being exploited: Huntress reported on November 16, 2026 that it confirmed in-the-wild exploitation of CVE-2026-84869. It observed one technician’s client run a guest-pushed batch file and another technician’s client open a guest-pushed text file. Huntress suggests looking for the ScreenConnect client on technician workstations running scripts from its Documents\...\Temp folder, and for Startup entries you didn’t add, such as Sync.bat. For the November activity, ConnectWise advises partners to preserve and review Run Command history, extension API activity, admin accounts, permission changes and Toolbox records. From a trusted device, revoke active ScreenConnect web sessions and associated identity-provider sessions, reset relevant credentials and enforce MFA. A password reset alone does not end all existing sessions. If you suspect compromise, isolate affected devices and preserve evidence. Use endpoint detection and response tools or another trusted out-of-band method to investigate and remediate affected devices. Include any technician workstations that connected to those devices. If a technician workstation was compromised, rotate all credentials accessible from it, including RMM, PSA, ScreenConnect, password vault and customer administrator credentials. Do not use ScreenConnect to investigate or clean suspected compromised endpoints. Clear unauthorized queued commands and tools, remove persistence and validate remediation before restoring connectivity.

U.S. federal agencies: CISA’s KEV entry set a September 14, 2026 due date. Covered agencies must apply the vendor’s mitigations, comply with BOD 26-04 and follow CISA’s forensic triage requirements. Follow the applicable cloud guidance or discontinue use if mitigations are unavailable.

CVE-2025-3935: ViewState code injection

ScreenConnect 25.2.3 and earlier may be open to a ViewState code injection attack. An attacker needs the server’s ASP.NET machine keys. ConnectWise says extracting them from the server takes privileged system-level access. Treat keys that have already been exposed as compromised. With the keys, an attacker could send a malicious ViewState to the server and possibly run code on it. NVD scores it 7.2 and ConnectWise 8.1 (CVSS 3.1). ConnectWise says it had no direct impact on the ScreenConnect client. CISA added it on June 2, 2025.

How to check if you’re affected: on the Version Check box, a server on 25.2.3 or earlier is affected unless it runs one of the patched older builds published April 22, 2025 or later.

CVE-2024-1708: path traversal

ScreenConnect 23.9.7 and prior have a path traversal flaw that may let an attacker execute remote code or directly impact confidential data or critical systems. NVD scores it 8.4 (CVSS 3.1). It was fixed in the same February 2024 release as CVE-2024-1709, but CISA only added it to its exploited list on April 28, 2026, and marks known ransomware use. A Microsoft Security Blog post of April 6, 2026 lists CVE-2024-1708 and CVE-2024-1709 among the flaws exploited by Storm-1175, a group that deploys Medusa ransomware.

  • Affected: ScreenConnect 23.9.7 and prior.
  • Fixed: 23.9.8 and later (bulletin of February 19, 2024). 22.4 note: the bulletin’s FAQ says the interim 22.4.20001 build fixes both 2024 flaws, but its later updates mention only CVE-2024-1709. Confirm with ConnectWise before relying on 22.4.20001 for this one.
  • Cloud: ConnectWise says cloud partners on screenconnect.com and hostedrmm.com were remediated and need no action.
  • On-premises: upgrade. Same steps as CVE-2024-1709 below.

How to check if you’re affected: a server on 23.9.7 or earlier is affected (see the 22.4 note above). ConnectWise also says to review installed extensions, and that .aspx or .ashx files in the server’s App_Extensions folder may be a sign this flaw was exploited.

CVE-2024-1709: authentication bypass

ScreenConnect 23.9.7 and prior have an authentication bypass. CISA says an attacker with network access to the management interface can create a new administrator-level account. NVD scores it 10.0 (CVSS 3.1), the maximum. CISA added it to its exploited list on February 22, 2024, and marks known ransomware use.

How to check if you’re affected: a server on 23.9.7 or earlier is affected unless it runs the interim 22.4.20001.8817 build or a later eligible patched build that ConnectWise says includes the CVE-2024-1709 fix. After patching for the two 2024 CVEs, ConnectWise says to review the configuration and user accounts, remove unrecognized users, change passwords and enable MFA. Validate installed extensions, remove and reinstall only those approved for use, and restart the server after completing these steps. Keep the extensions identified in the November 2026 advisory disabled.

Is ScreenConnect on my computer a sign of spying?

Not by itself. It is legitimate remote-support software. Here is how to find out who controls it.

ScreenConnect is legitimate remote-support software made by ConnectWise. Many IT providers install it so they can fix computers remotely. Scammers use it too, often after a call or email claiming your computer has a problem. ConnectWise’s advice is to never let someone access your machine unless you contacted them first.

  • See if it is installed (Windows): ConnectWise’s steps use Control Panel > Programs > Uninstall a program. You can also look under Settings > Apps > Installed apps on Windows 11, or Settings > Apps > Apps & features on Windows 10. Look for ScreenConnect Client (xxxxxxxxxxxxxxxx). ConnectWise says the code in brackets is a thumbprint unique to each ScreenConnect installation, so entries with different codes belong to different installations.
  • Find out who controls it: ask your IT provider or your company’s IT team if they installed it. On a work computer, contact your IT or security team before you remove anything, so they can preserve evidence and investigate.
  • Remove it if nobody you trust installed it: on a personal computer, uninstall the ScreenConnect Client entry you confirmed nobody you trust installed. If there are several entries and you can’t tell which is which, ask an IT provider. ConnectWise says that if a session is still open, you will be asked to close it; click Ok to continue.
  • If someone you didn’t authorize is controlling your computer: For a personal Windows computer, ConnectWise says to exit ScreenConnect from the system tray if you still have control. If you’ve lost control, disconnect the computer from the internet immediately and shut it down. On a work computer, disconnect it from the network and contact your IT or security team right away; follow their instructions before you shut it down.
  • If you think a scammer used it: report it through the public ScreenConnect Report Abuse page.

Not finding an entry doesn’t prove there is nothing there. Huntress has reported a script that installs a hidden ScreenConnect client and then removes its Windows uninstall entry. If you think your computer was taken over, ask an IT provider to check it.

ScreenConnect exploitation timeline

How to cut your ScreenConnect server’s exposure

Patching, client updates and disabling the RMM+ extensions come first. A blocklist only reduces how often attackers can try.

The standard ThreatListPro feed covers 5.4M+ IPv4 addresses from real attacks on live production Palo Alto GlobalProtect VPN portals in the US and is checked for new attackers every 6 hours. It loads on the firewall as a plain-text feed. You can test the free sample first, with no signup. To check one address, use the IP check tool.

Run ScreenConnect on-premises? The Secure ScreenConnect playbook is the step-by-step method we used to secure our own server. It is a $79 PDF for on-premises servers and adds to the vendor steps; it doesn’t replace them.

ScreenConnect vulnerability FAQs

How many ScreenConnect vulnerabilities are known to be exploited?

Four. As of November 18, 2026, CISA's Known Exploited Vulnerabilities catalog lists CVE-2026-84869, CVE-2025-3935, CVE-2024-1708 and CVE-2024-1709 for ConnectWise ScreenConnect. CISA marks known ransomware use for CVE-2024-1709 and CVE-2024-1708.

What is the latest ScreenConnect CVE?

The newest one in CISA's exploited list is CVE-2026-84869, a client flaw fixed in ScreenConnect 26.6.5 and added to the list on September 11, 2026. CVE-2026-127063, published November 12, 2026, is newer, but it is in the third-party RMM+ extension, not in the ScreenConnect server or client, and it is not in CISA's list.

Do I need to patch ScreenConnect Cloud?

ConnectWise says it has already updated its cloud-hosted ScreenConnect servers for all four exploited CVEs. Cloud partners still have work to do for CVE-2026-84869: reinstall host clients, update access agents and check that every technician workstation runs client 26.6.5 or later. ConnectWise's November 16, 2026 advisory requires that check for cloud and on-premises partners. On-premises servers must be upgraded by their owners.

How do I check my ScreenConnect version?

Sign in to your on-premises server as an administrator. ConnectWise's 26.6.5 bulletin points to Administration > Overview for your current and eligible version; its CVE-2025-3935 bulletin points to Administration > License > Version Check. A server older than 26.6.5 does not have the update for CVE-2026-84869. That flaw is in the client, so after upgrading, reinstall host clients, update access agents and check the client version on every technician workstation.

Is ScreenConnect on my computer a sign of spying?

Not by itself. ScreenConnect is legitimate remote-support software that many IT providers use. Scammers use it too. If you don't know who installed it, ask your IT provider. On a work computer, contact your IT or security team and follow their instructions so they can preserve evidence. On a personal computer, uninstall the ScreenConnect Client entry if you confirm nobody you trust installed it.

Does an IP blocklist fix ScreenConnect vulnerabilities?

No. Install the relevant ScreenConnect server and client updates. Keep the identified RMM+ extensions disabled pending ConnectWise guidance. A blocklist on the firewall in front of your server can reduce scanning and login attempts from known attacker addresses.

Block Known Attackers at Your Firewall

The standard ThreatListPro feed covers 5.4M+ IPv4 addresses and is checked for new attackers every 6 hours, as a plain-text feed for your firewall. Monthly is $19.99 with a 14-day free trial and no card needed.

Start a 14-day free trial

Sources

Primary sources reviewed November 18, 2026.

Related resources

ScreenConnect and remote-access reading.

ScreenConnect attacks, November 2026: what to do now Remote access security playbooks Security alerts: VPN, firewall and remote access attacks Check an IP address RDP Brute Force Protection