TL;DR: Apply ConnectWise's vendor-issued mitigations immediately in accordance with CISA's BOD 26-04 guidance; if mitigations are unavailable, discontinue use of the affected ScreenConnect client.
What Is the Vulnerability?
CVE-2026-84869 is a CVSS 9.9 Critical vulnerability affecting the ConnectWise ScreenConnect client. It was published to the National Vulnerability Database on 8 September 2026 and added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 11 September 2026.
The flaw is rooted in two distinct weakness categories:
- CWE-269 – Improper Privilege Management: The client does not correctly enforce privilege boundaries during an active remote session.
- CWE-862 – Missing Authorization: Certain code paths allow file-related operations to proceed without verifying that the requester is authorized to perform them.
According to the NVD description, 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." This means an attacker with access to an active remote session can potentially stage and run arbitrary files on the connected endpoint—without the Host (the person or system on the other side of the session) being prompted or approving the action.
The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H tells a stark story: the attack is network-reachable, requires low complexity, needs only low-level privileges, requires no user interaction, and has a Changed scope—meaning impact extends beyond the vulnerable component itself, with High ratings across Confidentiality, Integrity, and Availability.
Who and What Is Affected?
The vulnerability resides in the ConnectWise ScreenConnect client. ConnectWise has stated that ScreenConnect servers are not impacted by this flaw; the exposure is on the client side.
Organizations most at risk include:
- Managed Service Providers (MSPs) and IT teams that deploy ScreenConnect clients on customer or employee endpoints.
- Any organization whose endpoints run the ScreenConnect client and may have active or resumable remote sessions.
- Federal agencies subject to CISA's Binding Operational Directive (BOD) 26-04, which mandates prioritized remediation of KEV-listed vulnerabilities.
Because ScreenConnect is widely used for remote support and administration, the attack surface can be broad. Every endpoint with a ScreenConnect client installed that could participate in a remote session should be treated as potentially in scope until the vendor's mitigations are confirmed applied.
What Is the Potential Impact?
The practical consequence of this vulnerability is that an attacker who can interact with an active ScreenConnect remote session may be able to:
- Transfer arbitrary files to the endpoint without the Host's knowledge or consent.
- Execute those files on the endpoint, potentially deploying malicious payloads.
- Do all of the above without triggering a Host confirmation prompt, removing a key human-in-the-loop safeguard.
The Changed scope in the CVSS vector reflects that compromise of the ScreenConnect client can affect the broader endpoint and potentially the network it sits on—not just the ScreenConnect process itself. High impact ratings across Confidentiality, Integrity, and Availability suggest an attacker could read sensitive data, alter or destroy data, and disrupt system availability.
CISA's inclusion of this CVE in the KEV catalog confirms that exploitation has occurred in real-world environments. Organizations should treat this as an actively weaponized vulnerability, not a theoretical risk.
What Should You Do Right Now?
CISA's required action for KEV-listed vulnerabilities is clear and time-bound under BOD 26-04. The specific guidance for CVE-2026-84869 is:
- Apply vendor mitigations immediately. Follow ConnectWise's official advisory and instructions. Check the ConnectWise security advisories page for the most current guidance.
- Comply with BOD 26-04 patching timelines. Federal civilian executive branch agencies are legally required to meet these deadlines. Non-federal organizations are strongly encouraged to adopt the same urgency.
- Review CISA's Forensics Triage Requirements referenced in the KEV entry, particularly if you suspect any ScreenConnect sessions may have been active during the exposure window.
- For cloud-hosted ScreenConnect deployments, follow the applicable BOD 26-04 guidance for cloud services as directed by CISA.
- Discontinue use if mitigations are unavailable. If ConnectWise cannot provide or you cannot apply mitigations, CISA's required action explicitly states the product should be discontinued until it can be secured.
- Audit active and recent remote sessions. Identify any sessions that were open during the vulnerability window and review endpoint activity logs for unauthorized file transfers or executions.
- Restrict session access. Until mitigated, limit who can initiate or connect to ScreenConnect sessions, and prefer session-level controls that reduce exposure to unknown or untrusted parties.
Primary references for remediation: CISA KEV Catalog, ConnectWise's own security advisory page, and NVD entry for CVE-2026-84869.
How External Testing Surfaces This Exposure
Understanding whether your organization is exposed to CVE-2026-84869 requires knowing the precise scope of your ScreenConnect client deployments—and that is often harder than it sounds.
External attack-surface assessments can help by:
- Identifying internet-facing ScreenConnect infrastructure associated with your organization, including relay endpoints and any externally reachable management interfaces.
- Detecting unpatched or unmitigated client versions where version fingerprinting is possible through banner information or protocol responses.
- Mapping endpoints that may be reachable from the internet and therefore accessible to a broader set of potential attackers, not just insiders.
- Flagging configuration weaknesses such as overly permissive session policies that could increase the practical exploitability of this flaw.
Because this flaw is in the client rather than the server, the exposure surface is distributed across every managed endpoint—not concentrated in one place. Point-in-time external scans are most useful when combined with an internal inventory of all ScreenConnect client deployments so that gaps between what is visible externally and what exists internally can be reconciled.
If your organization uses ScreenConnect as part of a managed service or outsourced IT arrangement, ensure your service provider can demonstrate that client-side mitigations have been applied to all endpoints under their management.
Sources & further reading: NVD CVE-2026-84869 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: github.com, connectwise.com, connectwise.com, cisa.gov. This advisory contains no exploit code.
Frequently asked questions
Are ScreenConnect servers vulnerable to CVE-2026-84869?
No. According to ConnectWise, ScreenConnect servers are not impacted by this vulnerability. The flaw resides in the ScreenConnect client component.
Is this vulnerability being actively exploited?
Yes. CISA added CVE-2026-84869 to the Known Exploited Vulnerabilities catalog on 11 September 2026, which indicates confirmed exploitation in real-world environments. Organizations should treat this as an active threat.
What privileges does an attacker need to exploit this flaw?
The CVSS 3.1 vector indicates that only low-level privileges are required (PR:L). The attack is network-based, requires low complexity, and needs no user interaction, making it relatively easy to exploit once access to an active session is obtained.
What if we cannot apply the vendor's mitigations right away?
CISA's required action explicitly states that if mitigations are unavailable, organizations should discontinue use of the product. This is particularly binding for federal agencies under BOD 26-04, but all organizations should weigh the risk of continued use against the operational need.