ConnectWise ScreenConnect path traversal keeps remote-support tooling in the attacker playbook
CISA listed this issue as known exploited. The useful SOC question is where the affected system sits, what it can reach, and whether logs can prove if it was touched.
ConnectWise ScreenConnect path traversal keeps remote-support tooling in the attacker playbook
CVE-2024-1708 went into CISA KEV on 2026-04-28. That moves it out of the theoretical pile.
The affected product is ConnectWise ScreenConnect. CISA describes the issue as ConnectWise ScreenConnect Path Traversal Vulnerability. In plainer terms: ConnectWise ScreenConnect contains a path traversal vulnerability which could allow an attacker to execute remote code or directly impact confidential data and critical systems.
Remote access tooling is already an approved way through the wall. That is why compromise here is so useful.
Why it matters
Remote-support tools are high-value because they are meant to cross boundaries. They already have the trust, agents, and access an intruder would otherwise need to build by hand.
This is where vulnerability management often falls over. Teams record the CVE, ask for a patch date, and move on. That works for low-value software. It does not work for systems that manage identity, remote access, endpoints, build pipelines, network policy, backups, observability, or customer-facing applications.
The better question is what an attacker gets after exploiting it. Shell access is bad. Access to a management console, token store, CI runner, or edge controller is worse because it can turn one bug into a path through the estate.
First checks
Review technician accounts, API keys, session history, uploaded files, agent deployments, and any change that created or widened remote access.
Ask four questions before closing the ticket:
- Is it deployed anywhere, including old lab, DR, MSP, and vendor-managed environments?
- Is any instance reachable from the internet or a broad internal network?
- Which accounts, tokens, certificates, or integrations does it hold?
- Can the logs show exploitation attempts, successful use, and post-exploitation changes?
If one of those answers is missing, record that as a gap. Do not bury it in the patch ticket. Future incident responders will not appreciate the archaeological dig.
Hunt notes
Start with the boring evidence:
- new or rare administrator logins
- access from unusual ASNs, VPN pools, jump hosts, or user subnets
- new users, API keys, service accounts, scheduled tasks, webhooks, connectors, or tunnels
- configuration exports, backup downloads, disabled logging, or policy edits
- unexpected child processes, shell commands, archive creation, or outbound callbacks
- user agents and API calls that do not match normal admin tooling
For internet-facing systems, keep the hunt window wider than the patch window. Public exploit activity often starts before the internal meeting invite appears. A shocking development, I know.
S6 view
This belongs in the same 2026 pattern as the other KEV additions: attackers keep aiming at control points. Firewalls, SD-WAN managers, endpoint consoles, remote access platforms, developer tools, and AI gateways all share the same problem. Other systems trust them.
The practical test is simple: can the team name the owner, find every instance, patch or isolate it, and prove from logs whether anyone got there first?
