nday
CVE-2026-84869

ScreenConnect Client: Guest-to-Host File Execution via File-Transfer Actions

ConnectWise / ScreenConnect

Added to KEV 3 days after disclosure. nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

broken access control
CWE-862, stated by the CNA ConnectWise and NVD, republishing 7d616e1a-3288-43b1-a0dd-0a65d3e70a49
improper privilege management
CWE-269, stated by the CNA ConnectWise and NVD, republishing 7d616e1a-3288-43b1-a0dd-0a65d3e70a49
network
AV:N in CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H (CVSS 3.1) from the CNA ConnectWise
no user interaction
UI:N in CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H (CVSS 3.1) from the CNA ConnectWise
ConnectWise ScreenConnect
affected products in the CVE record: ConnectWise · ScreenConnectCPE names NVD's analysts give as vulnerable: a:connectwise:screenconnect
remote desktop / remote access
affected products in the CVE record: ConnectWise · ScreenConnectCPE names NVD's analysts give as vulnerable: a:connectwise:screenconnectthe product type of ConnectWise ScreenConnect in nday's product registry
stage
KEV
disclosed
disclosure → KEV
T+3d KEV is date-only
cvss
9.9 CRITICAL v3.1
KEV due date
2026-09-14

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
09-08T19:29Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
≤ 09-11, inferred from KEV
KEVKEV
09-11, date only

Summary

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.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:L
Low: ordinary user privileges
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

CVSS 3.1 vector from the CVE record, scored by the CNA ConnectWise.

Event log

+DISdisclosed

CVE record published by ConnectWise. CVSS 9.9, critical. CISA's SSVC assessment rates exploitation as active.

src cvelist · nday , bulk import · raw
{
  "id": 17985,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-84869",
  "occurred_at": "2026-09-08T19:29:33.63Z",
  "observed_at": "2026-11-12T15:01:53.938848Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "kev": {
      "reference": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-84869",
      "date_added": "2026-09-11"
    },
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
      "version": "3.1",
      "base_score": 9.9,
      "base_severity": "CRITICAL"
    },
    "ssvc": {
      "timestamp": "2026-09-10T00:00:00+00:00",
      "automatable": "no",
      "exploitation": "active",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2026-09-08T19:29:33.630Z",
    "assigner_short_name": "ConnectWise"
  }
}
2026-09-11date only, from source
+KEVadded to KEV

CISA added it to the Known Exploited Vulnerabilities catalog, with a remediation deadline of 2026-09-14, and calls for forensic triage. Ransomware use: unknown.

src kev · nday , bulk import · raw
{
  "id": 71,
  "type": "kev_added",
  "source": "kev",
  "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog",
  "occurred_at": "2026-09-11T00:00:00Z",
  "observed_at": "2026-11-12T13:53:00.018191Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cwes": [
      "CWE-269",
      "CWE-862"
    ],
    "notes": "https://www.connectwise.com/company/trust/security-bulletins/2026-09-08-screenconnect-bulletin ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-84869",
    "product": "ScreenConnect",
    "due_date": "2026-09-14",
    "precision": "day",
    "date_added": "2026-09-11",
    "vendor_project": "ConnectWise",
    "forensic_triage": "Yes",
    "required_action": "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.",
    "vulnerability_name": "ConnectWise ScreenConnect Improper Privilege Management and Missing Authorization Vulnerability",
    "known_ransomware_campaign_use": "Unknown"
  }
}
≤ 2026-09-11inferred, no direct source
~ITWexploited in the wild

No source says when exploitation began. A KEV listing means it was already happening, so only an upper bound is known. CISA's SSVC assessment rates exploitation as active.

based on kev and CISA's assessment in cvelist

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

1 researcher mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

  1. 2026-11-17

    Post by @DailyDarkWeb on 2026-11-17. Sign in to read it.

Sign in to read 1 post.

sign in to read

Discussion

0 comments

No comments yet.