Attackers are actively abusing ConnectWise ScreenConnect CVE-2026-84869 to run malicious files on managed service provider (MSP) technician workstations without showing a confirmation prompt when the technician joins a remote session. The flaw carries CVSS 9.9, lives in the host client (not the server), and landed in CISA's Known Exploited Vulnerabilities catalog on September 11, 2026. ConnectWise's September 8 bulletin fixes it in ScreenConnect 26.6.5, but November reporting describes confirmed technician takeovers where a guest-pushed batch file executed in roughly nine seconds—often on machines that also hold customer admin credentials, password vaults, and local copies of coding-agent API keys.
If you develop with Claude Code, Codex, or MCP-heavy IDEs on a laptop your MSP can remote into, this is not abstract RMM news. It is the same privilege surface as N-able N-central's Able2Shell emergency: infrastructure remote access becomes silent code execution on the keyboard you type agent prompts with.
TL;DR
| Question | Answer |
|---|---|
| Am I affected? | Yes if any ScreenConnect host client on a machine you use is below 26.6.5, especially MSP technician or Access endpoints |
| Is there a fix? | ScreenConnect 26.6.5+; reinstall host clients and update Access agents after server upgrade |
| Exploited in the wild? | Yes — CISA KEV (added 2026-09-11); November 2026 confirmed MSP incidents reported publicly |
| Severity | CVSS 9.9 — network, low complexity; missing authorization on guest file execution () |
| Emergency mitigation | Remove TransferFiles permission from all roles until patched (ConnectWise bulletin) |
| Does Beam block this? | No — Beam does not patch RMM clients or filter ScreenConnect traffic |
What ConnectWise and CISA document
ConnectWise's security bulletin, dated September 8, 2026, describes CVE-2026-84869 as a condition that may allow files to be transferred and executed through an active remote session without authorization or host confirmation in certain circumstances. ScreenConnect servers are not impacted. The patch 26.6.5 strengthens client and session handling for file-transfer and file-execution actions.
The bulletin lists:
| CWE | Role in the flaw |
|---|---|
| CWE-862 (Missing Authorization) | Guest actions that should require host confirmation do not |
| CWE-269 (Improper Privilege Management) | Execution can occur with elevated context in the described scenarios |
ConnectWise rates severity Important but priority 1 — High because the vulnerability is being targeted or has higher risk of targeting in the wild. That pairing is why federal purchasers treat it as urgent even before November's technician-case reporting.
CISA's KEV entry mirrors the impact: an attacker may transfer and execute files through an active session without authorization or host confirmation. CISA added the CVE on 2026-09-11 with due date 2026-09-14 and forensic triage expectations under BOD 26-04. Ransomware use is listed unknown; that does not imply absence of commodity intrusion.
Affected versions: anything prior to 26.6.5. Cloud ScreenConnect instances were upgraded automatically, but ConnectWise still tells partners to reinstall host clients and update access agents after upgrading—because the vulnerable software often sits on technician laptops, not only the hosted server.
Temporary mitigation when patching must wait: under Administration > Security > Roles, edit each role, review session groups, and deselect TransferFiles where it is enabled. ConnectWise warns this is not a substitute for 26.6.5.
Attack chain, step by step
Huntress confirmed the November technician compromises described below; Cyber Security News published a recap on November 17, 2026. We did not reproduce the exploit; the steps follow ConnectWise's bulletin plus Huntress's published incident narrative.
- Attacker obtains guest presence in a Support or Access session—either by controlling a customer endpoint already in a session or by joining as an additional guest in a legitimate customer queue.
- Technician joins the same session to provide remote help. No extra click is required from the technician beyond opening the session; the vulnerable client trusts guest-originated file execution in that window.
- Guest transfers a file (reported examples use batch scripts in the client's temporary folder) and triggers execution without a confirmation prompt.
- Payload stages persistence: described November campaigns used PowerShell with a hidden window, downloaded an MSI disguised as a Windows Update component, and installed a rogue ScreenConnect-compatible client pointed at an attacker relay.
- Attacker inherits technician context: MSP tooling, saved credentials, browser sessions, and local developer files—the same disk trees coding agents read when you run Claude Code or Codex locally.
The mechanic that makes this worse than generic phishing is trust in the support session. The technician expects remote control software to move files; CVE-2026-84869 removes the host confirmation gate for execution in affected builds.
Researchers also describe high-volume delivery attempts between October 20 and November 16, 2026—hundreds of thousands of guest run-batch requests across dozens of MSP servers—most of which are spray, not proof that every attempt succeeded. Treat that as noise plus at least one confirmed compromise, not as a count of infected laptops.
Timeline
| Date | Event |
|---|---|
| 2026-09-08 | ConnectWise publishes 26.6.5 security patch bulletin for CVE-2026-84869 |
| 2026-09-11 | CISA adds to KEV; due date 2026-09-14 |
| 2026-09-12 | NVD and Beam CVE sync record updated metadata |
| 2026-10-20 – 2026-11-16 | Reported guest batch delivery waves against MSP servers |
| 2026-11-12 | Reported confirmed technician workstation compromise (~9 seconds to rogue client) |
| 2026-11-17 | Broad security press recap of active exploitation |
If your change board deferred 26.6.5 because "the cloud server auto-patched," the timeline explains why that decision left endpoints behind.
Who is affected
Directly affected:
- MSP technicians running ScreenConnect host clients below 26.6.5
- Organizations using ConnectWise Control / ScreenConnect Access agents on helpdesk or field laptops
- Customers indirectly, when compromised technician hosts become launch points into tenant RMM, vaults, and customer networks
Not affected (per vendor):
- ScreenConnect server software alone — the bulletin states servers are not impacted; risk is client-side
Developer / coding-agent overlap:
- Laptops tagged for "VIP developer" support in RMM
- Machines with lend-style remote agents SSH back to a local gh or op socket
- Workstations storing
.env, MCP configs, and Claude/Codex credential files beside MSP inventory agents
No AI product is required for exploitation. The page tracks severity and KEV metadata for patch prioritization.
How to check and patch
1. Confirm build 26.6.5 or newer
On-premises partners:
- Open Administration > Overview on the ScreenConnect server and verify 26.6.5+ eligibility.
- Download from ConnectWise's Download | ScreenConnect page (license required).
- Follow ConnectWise's upgrade an on-premises installation documentation in the bulletin.
Technician endpoints (critical):
- After server upgrade, reinstall host clients and update Access agents on every technician machine—not only the server VM.
Cloud ScreenConnect:
- Server side is already current; still audit each technician client build in your endpoint inventory.
2. Apply mitigation if patch windows slip
Until every host client is on 26.6.5:
- Administration > Security > Roles
- For each role, open session groups and deselect TransferFiles
- Save and repeat for all roles
Document the mitigation with an expiry date; ConnectWise treats it as exposure reduction, not remediation.
3. Investigate for compromise
ConnectWise's compromised-instance FAQ (linked from the bulletin) recommends isolating suspects, preserving images, resetting passwords, reviewing audit logs, forcing technician re-login, and enabling MFA.
Add developer-specific checks:
- Unexpected
ScreenConnect.Client.exechildren launching PowerShell or cmd from%TEMP% - New
Windows Update Agentpaths under%LOCALAPPDATA%that are not Microsoft-signed - Startup folder drops (reported traversal-style paths toward Sync.bat in Startup)
- Recent edits to agent config directories after support sessions you did not initiate
If compromise is likely, follow the same key rotation discipline as provider console breaches: assume tokens on disk were readable.
4. MSP customers: ask direct questions
- Which host client build is installed on machines that touch our repository credentials?
- Were TransferFiles permissions removed during the mitigation window?
- Is remote support disabled on developer workstations unless ticketed?
What this means if you run AI coding agents
Coding agents amplify workstation integrity. They routinely:
- Read project roots and home-directory configs
- Execute shell commands with your user privileges
- Store API keys in plaintext files many teams forget to exclude from RMM inventory
A compromised MSP laptop is therefore a prompt-injection-free path to agent secrets: the attacker does not need to trick the model if they already run PowerShell as the technician.
Concrete habits:
- Segment: run agents on hosts without persistent ScreenConnect host clients when possible; use Beam MDM inventory on enrolled laptops to confirm which machines still carry vendor-installed remote-support agents.
- Log locally: keep agent monitoring on endpoints where enforce policy matters, so post-incident review shows what tools ran after a support window.
- Rotate after RMM incidents: any confirmed ScreenConnect compromise on a box that ever held ANTHROPIC_API_KEY, OPENAI_API_KEY, or MCP OAuth refresh tokens triggers rotation, not "wait for customer notice."
- Do not forward unlimited SSH: if you use remote dev VMs, prefer policy-gated agents (lend) over leaving ssh-agent wide open on a support-controlled laptop.
This CVE does not change model weights or MCP wire formats. It changes who can execute code on the machine beside your agent.
Comparison to other KEV issues on shared networks
FreeSWITCH CVE-2026-116779 showed how daemon RCE on a adjacent VLAN pivots toward developer keys. ScreenConnect is the human support lane equivalent: interactive, trusted, and often excluded from EDR scrutiny because it is "IT tooling."
Both belong in the same review queue when you map CISA KEV items against workstations that run agents.
What Beam can and cannot do here
Beam is local observability and optional hook-based deny for Claude Code and Codex tool use—credential-pattern redaction, skill/MCP heuristics, and workspace policy on the machine where the collector runs. It does not:
- Patch or version-check ScreenConnect binaries
- Intercept RMM file transfers
- Distinguish legitimate technician scripts from attacker batch files without you defining risky command patterns
If an attacker already runs code outside the agent harness, Beam may still capture subsequent agent tool calls, but that is after compromise. Treat Beam as evidence and guardrails on agent behavior, not a replacement for 26.6.5 and MSP hygiene.
Frequently asked questions
The front matter lists direct answers on exploitation status, version checks, and ConnectWise safety questions people search after KEV headlines. If your MSP has not confirmed client builds in writing, assume host clients are outstanding until you see 26.6.5 on the technician endpoint itself.
Related reading
- N-able Able2Shell and developer endpoints
- FreeSWITCH KEV on shared lab networks
- lend: keep credentials on the laptop during remote agents
- What agent monitoring software tracks locally
- November 2026 attacks timeline
- ConnectWise trust center bulletin (primary vendor)
- Huntress: MSP technician exploitation (incident research)
- CISA KEV: CVE-2026-84869
Version numbers, KEV dates, and ConnectWise mitigation steps reflect vendor and CISA publications as of November 17, 2026. Beam does not operate ScreenConnect infrastructure; confirm builds with your MSP or internal IT record.

