CVE-2026-84869
KEVConnectWise ScreenConnect Improper Privilege Management and Missing Authorization Vulnerability
Description
ConnectWise ScreenConnect contains both an improper privilege management and missing authorization vulnerability that may allow an attacker to transfer and execute files through an active remote session without authorization or host confirmation.
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. ScreenConnect servers are not impacted.
CVSS 3.1 vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HPublishedSep 8, 2026
Last modifiedSep 12, 2026
Added to KEVSep 11, 2026
Remediation dueSep 14, 2026
References
- github.com/ConnectWise-Advisories/Disclosures/tree/main/CVE-2026-84869Third Party Advisory
- connectwise.com/company/trust/advisoriesVendor Advisory
- connectwise.com/company/trust/security-bulletins/2026-09-08-screenconnect-bulletinVendor Advisory
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-84869US Government Resource
- huntress.com/blog/rogue-screenconnect-installationsThird Party Advisory
0 recent articles mention this CVE
80
Risk assessment · Critical
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 42 days
- CVSS
- 9.9 CRITICAL
- EPSS (30-day exploit probability)
- 0.92% · top 40% of all CVEs
- Weakness
- CWE-269
- Attack vector
- Network, remotely reachable
Recommended actions
- 1.Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.