CVE-2026-84869 — ConnectWise ScreenConnect Improper Privilege Management and Missing Authorization Vulnerability

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

CISA required action CISA

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.

US federal deadline: Sep 14, 2026 — passed 31 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

1. Identify exposed assets running the affected vendor/product/version combinations (Connectwise Screenconnect).
2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
4. Search available logs for exploit probes matching the vulnerability class (privilege escalation), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-269 · Improper Privilege Management

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

EPSS over time FIRST

Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 0.92%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

• Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
• Hunt retroactively in logs from before Sep 11, 2026 (KEV listing): exploitation may have started earlier.

Timeline

What happened to this CVE, newest first.

• 2026
• Affected products added · connectwise/screenconnect
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• SSVC assessment updated
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• Record published
  Oct 13, 2026
• Affected products added · connectwise/screenconnect
  Oct 13, 2026 · NIST National Vulnerability Database
• CVSS changed · 9.9
  Oct 13, 2026 · NIST National Vulnerability Database
• Source status changed · → Analyzed
  Oct 13, 2026 · NIST National Vulnerability Database
• Added to CISA KEV (detected)
  Oct 13, 2026 · CISA Known Exploited Vulnerabilities
• Record created in this database
  Oct 13, 2026 · CISA Known Exploited Vulnerabilities
• Added to CISA KEV catalog
  Sep 10, 2026 · CISA
• CVE published
  Sep 8, 2026 · ConnectWise

Source activity

Repeated readings are counted rather than listed.

• 2× References added · Oct 13, 2026 – Oct 13, 2026
• 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

7 on the record

• www.connectwise.com/company/trust/advisories
  Vendor Advisory, NIST National Vulnerability Database
• www.connectwise.com/company/trust/security-bulletins/2026-09-08-screenconnect-bulletin
  Vendor Advisory, NIST National Vulnerability Database
• www.cisa.gov/known-exploited-vulnerabilities-catalog
  US Government Resource, NIST National Vulnerability Database
• nvd.nist.gov/vuln/detail/CVE-2026-84869
  GitHub Security Advisories
• github.com/advisories/GHSA-rc8v-f46m-jcgm
  GitHub Security Advisories
• www.huntress.com/blog/rogue-screenconnect-installations
  Third Party Advisory, NIST National Vulnerability Database
• github.com/ConnectWise-Advisories/Disclosures/tree/main/CVE-2026-84869
  Third Party Advisory, NIST National Vulnerability Database

Elsewhere on this site

Related CVEs (same products)

• Medium CVE-2026-11596 In ScreenConnect™ versions prior to 26.2, input validation within the Host Pass creation… Jun 10, 2026
• Critical CVE-2026-3564 ScreenConnect Instance Level Cryptographic Material Exposure Mar 17, 2026
• Medium CVE-2025-14823 Certificate Signing Extension Returns Encrypted Values Dec 18, 2025
• Critical CVE-2025-14265 Improper server-side validation in ScreenConnect extension framework Dec 11, 2025
• High CVE-2025-3935 ConnectWise ScreenConnect Improper Authentication Vulnerability KEV Apr 25, 2025
• High CVE-2024-1708 ConnectWise ScreenConnect Path Traversal Vulnerability KEV Feb 21, 2024

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

• No fixed version, patch or mitigation documented.
• No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
• No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
• No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-84869 is "ConnectWise ScreenConnect Improper Privilege Management and Missing Authorization Vulnerability", rated Critical. It affects Screenconnect (Connectwise); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 9.9 describes technical severity. EPSS 0.92% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.