<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Rmm | FirewallSync</title><link>https://firewallsync.com/tags/rmm/</link><description>Practical cybersecurity writing for engineering teams that ship fast.</description><language>en-us</language><image><url>https://firewallsync.com/icon-512.png</url><title>FirewallSync</title><link>https://firewallsync.com/</link></image><lastBuildDate>Sun, 15 Nov 2026 04:55:00 +0000</lastBuildDate><atom:link href="https://firewallsync.com/tags/rmm/index.xml" rel="self" type="application/rss+xml"/><item><title>ScreenConnect SCKit Worm via RMM+ Extension: What We Know</title><link>https://firewallsync.com/posts/screenconnect-sckit-worm-rmm-plus-extension-what-we-know/</link><guid>https://firewallsync.com/posts/screenconnect-sckit-worm-rmm-plus-extension-what-we-know/</guid><pubDate>Sun, 15 Nov 2026 04:55:00 +0000</pubDate><dc:creator>John Marshall</dc:creator><category>Security Operations</category><description>Huntress reports rogue ScreenConnect clients and an SCKit toolkit on 288 hosts at 48 organizations on November 11, 2026 and 205 more hosts at 41 organizations on November 13. ConnectWise disabled five third-party extensions, including RMM+, across about 400 partner environments. What is confirmed, what is not, and what to check.</description><enclosure url="https://firewallsync.com/posts/screenconnect-sckit-worm-rmm-plus-extension-what-we-know/cover_hu9712551773197380682.jpg" type="image/jpeg" length="0"/><media:content url="https://firewallsync.com/posts/screenconnect-sckit-worm-rmm-plus-extension-what-we-know/cover_hu9712551773197380682.jpg" medium="image" type="image/jpeg" width="1200" height="630"/><content:encoded><![CDATA[<p><img src="https://firewallsync.com/posts/screenconnect-sckit-worm-rmm-plus-extension-what-we-know/cover_hu9712551773197380682.jpg" alt="Close-up of a wiring frame densely packed with red, yellow, green and white wires on terminal pins" width="1200" height="630"></p><p><strong>What happened:</strong> On November 11, 2026, security firm Huntress saw rogue ScreenConnect clients appear on customer endpoints at 48 organizations within about 90 minutes, followed by a toolkit it calls <strong>SCKit</strong>. A second wave on November 13 hit 205 more hosts across 41 organizations. ConnectWise, which makes ScreenConnect, says it has found no compromise of its own infrastructure and no flaw in ScreenConnect itself, and has disabled five third-party extensions, including one called <strong>RMM+</strong>, across about 400 partner environments. How the attackers first got in is not yet confirmed.</p>
<p>ScreenConnect is remote-support software widely used by managed service providers (MSPs) and IT teams, so a single compromised console can reach every machine it manages. It is the second incident this week involving MSP remote-management software, after the <a href="/posts/n-able-n-central-able2shell-zero-days-offline-what-we-know/">N-able N-central Able2Shell zero-days</a>.</p>
<h2 id="timeline">Timeline</h2>
<p>Times are UTC as given by <a href="https://www.huntress.com/blog/sckit-worm-rogue-screenconnect">Huntress</a> unless noted.</p>
<table>
  <thead>
      <tr>
          <th>Date</th>
          <th>Event</th>
          <th>Source</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Aug-Sep 2026</td>
          <td>Earlier rogue ScreenConnect &ldquo;worm-like&rdquo; activity; Huntress Rapid Response</td>
          <td><a href="https://huntress.com/blog/rogue-screenconnect-installations">Huntress (Sept post)</a></td>
      </tr>
      <tr>
          <td>Sep 8, 2026</td>
          <td>ConnectWise publishes CVE-2026-84869 (CVSS 9.9), fixed in ScreenConnect 26.6.5</td>
          <td>CVE record</td>
      </tr>
      <tr>
          <td>Sep 11, 2026</td>
          <td>CISA adds CVE-2026-84869 to KEV</td>
          <td><a href="https://www.cisa.gov/known-exploited-vulnerabilities-catalog">KEV catalog</a></td>
      </tr>
      <tr>
          <td>Nov 11, ~17:47</td>
          <td>Huntress first observes suspicious activity; all 288 hosts hit within about 90 minutes</td>
          <td>Huntress</td>
      </tr>
      <tr>
          <td>Nov 11, 22:45</td>
          <td>ConnectWise publishes its advisory</td>
          <td>Huntress</td>
      </tr>
      <tr>
          <td>By Nov 12</td>
          <td>ConnectWise disables five RMM+-family extensions across about 400 partner environments</td>
          <td>Huntress, <a href="https://cyberscoop.com/connectwise-screenconnect-sckit-attack/">CyberScoop</a>, <a href="https://www.theregister.com/security/2026/11/12/hackers-exploiting-screenconnect-plugin-flaw-to-spread-malware-across-hundreds-of-pcs/5309361">The Register</a></td>
      </tr>
      <tr>
          <td>Nov 13, 16:12</td>
          <td>Second wave detected: 205 hosts across 41 organizations</td>
          <td>Huntress (update 5:30pm ET)</td>
      </tr>
  </tbody>
</table>
<h2 id="confirmed-vs-not-confirmed">Confirmed vs not confirmed</h2>
<table>
  <thead>
      <tr>
          <th>Claim</th>
          <th>Status</th>
          <th>Who says so</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>288 hosts across 48 organizations hit on Nov 11</td>
          <td>Reported</td>
          <td>Huntress, from its own customer telemetry</td>
      </tr>
      <tr>
          <td>205 hosts across 41 organizations hit on Nov 13</td>
          <td>Reported</td>
          <td>Huntress</td>
      </tr>
      <tr>
          <td>No compromise of ConnectWise infrastructure or vulnerability in ScreenConnect itself</td>
          <td>Vendor statement</td>
          <td>ConnectWise, quoted by CyberScoop and The Register</td>
      </tr>
      <tr>
          <td>Five third-party extensions disabled across about 400 environments</td>
          <td>Vendor action</td>
          <td>ConnectWise, via Huntress, CyberScoop, The Register</td>
      </tr>
      <tr>
          <td>The ~400 environments are compromised</td>
          <td><strong>No.</strong> ConnectWise says they were flagged for having the extensions, not for confirmed compromise</td>
          <td>The Register</td>
      </tr>
      <tr>
          <td>RMM+ was the initial access vector</td>
          <td><strong>Not confirmed.</strong> Huntress calls the link suggestive; ConnectWise had &ldquo;not yet identified an initial access vector and full scope&rdquo;</td>
          <td>Huntress</td>
      </tr>
      <tr>
          <td>Spread from technician workstations to other customers</td>
          <td><strong>Not observed succeeding.</strong> Huntress reconstructed the capability but did not see it work in the logs it checked</td>
          <td>Huntress</td>
      </tr>
      <tr>
          <td>Who did it</td>
          <td><strong>Not attributed</strong></td>
          <td>Huntress, CyberScoop</td>
      </tr>
  </tbody>
</table>
<p>Huntress&rsquo;s counts come from organizations that use Huntress. The total number of affected organizations is not known publicly, and the two waves&rsquo; organization counts should not be added together, since the same organization could appear in both.</p>
<h2 id="how-the-attack-worked-as-far-as-sources-say">How the attack worked, as far as sources say</h2>
<p><strong>Suspected entry point.</strong> Huntress says the activity &ldquo;seems to be related&rdquo; to RMM+ versions 1.0.31 and 1.0.32. The Register, reporting the same finding, says &ldquo;installations without a configured access key will accept a blank one.&rdquo; Per Huntress, RMM+ operates outside ScreenConnect&rsquo;s user accounts, roles and MFA, and it found no matching login activity in incident logs; the commands appeared in logs linked to RMM+. Huntress also says most RMM+ installations it saw were legitimate. The extension&rsquo;s developer has not been named in any of the reports we read.</p>
<p><strong>What was installed.</strong> According to Huntress:</p>
<ul>
<li>A rogue ScreenConnect client, installed silently by a batch-script dropper.</li>
<li>SCKit, about 16 files delivered as an encrypted package with keys tied to the victim machine&rsquo;s UUID.</li>
<li>&ldquo;RelayTrap&rdquo; components that take over the legitimate client&rsquo;s connection slot, plus a <code>TrapWatch</code> scheduled task running as SYSTEM.</li>
<li>Defender exclusions, AppLocker/SRP rules and, in one incident, a service posing as &ldquo;Windows Update Agent&rdquo;.</li>
<li>A <code>netsh portproxy</code> rule, a modified hosts file, and a tool that steals browser session cookies, including ScreenConnect&rsquo;s <code>.aspxauth</code> cookie, which Huntress describes as a way to reach further sessions.</li>
</ul>
<p>Huntress also warns that isolating a host does not remove this persistence, and that infected systems were reinfected soon after isolation ended.</p>
<p><strong>How it relates to CVE-2026-84869.</strong> The September flaw lets files be &ldquo;transferred and executed through an active remote session without authorization or Host confirmation in certain circumstances,&rdquo; per the <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/84xxx/CVE-2026-84869.json">CVE record</a>, and affects &ldquo;All versions prior to 26.6.5&rdquo;. ConnectWise&rsquo;s November guidance tells partners to confirm every technician client runs 26.6.5 or later. Neither ConnectWise nor Huntress says the November campaign exploited this CVE, so treat the upgrade as hardening against the spread path, not as the root cause.</p>
<h2 id="what-to-check-in-your-environment">What to check in your environment</h2>
<p>If you run ScreenConnect, cloud or on-premises:</p>
<ol>
<li><strong>Extensions.</strong> Check for Labtech Plus, RMM Plus, RMM+, RMM Plus Password Link and RMM+ Password Link. ConnectWise disabled them on hosted instances; on-premises partners must disable them themselves.</li>
<li><strong>Client versions.</strong> Confirm technician clients are on 26.6.5 or later.</li>
<li><strong>Do not triage through ScreenConnect.</strong> Huntress advises against connecting to a suspect host through ScreenConnect and recommends WinRM or another out-of-band tool. If a technician already connected to a suspect host, investigate that technician&rsquo;s workstation from a clean device.</li>
<li><strong>Hunt for the artefacts Huntress lists:</strong> an unfamiliar ScreenConnect client alongside the legitimate one, a <code>TrapWatch</code> scheduled task, <code>C:\ProgramData\RelayTrap\</code>, toolkit files in <code>%TEMP%</code>, a <code>RelayTrapLiteAlert</code> Run value, unexpected <code>netsh interface portproxy</code> rules, and hosts-file changes. Huntress publishes hashes and network indicators in its post.</li>
<li><strong>Sessions and credentials.</strong> Terminate active ScreenConnect web sessions, rotate credentials, and revoke browser and identity-provider sessions.</li>
<li><strong>Audit history.</strong> Review Run Command and Toolbox history and instance audit logs for activity with no matching user login.</li>
</ol>
<p>For engineers outside the MSP world, the transferable lesson is about plugins: any extension that runs commands with its own authentication path is a second front door to your remote-access tool. Inventory extensions with the same rigour as user accounts, and require that their access keys are set rather than defaulting to empty. For tracking the ScreenConnect CVEs already in KEV, see <a href="/posts/cisa-kev-json-feed-what-each-field-means-and-how-to-match-it-against-a-scanner-export/">how to match the CISA KEV JSON feed against a scanner export</a>.</p>
<h2 id="sources-and-verification">Sources and verification</h2>
<table>
  <thead>
      <tr>
          <th>Important claim</th>
          <th>Source</th>
          <th>Status</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Counts, timeline, RMM+ versions, toolkit components, recommendations</td>
          <td><a href="https://www.huntress.com/blog/sckit-worm-rogue-screenconnect">Huntress, Nov 11 2026, updated Nov 13</a></td>
          <td>Verified (Huntress telemetry)</td>
      </tr>
      <tr>
          <td>ConnectWise found no infrastructure compromise or ScreenConnect vulnerability</td>
          <td><a href="https://cyberscoop.com/connectwise-screenconnect-sckit-attack/">CyberScoop, Nov 12 2026</a>, <a href="https://www.theregister.com/security/2026/11/12/hackers-exploiting-screenconnect-plugin-flaw-to-spread-malware-across-hundreds-of-pcs/5309361">The Register, Nov 12 2026</a></td>
          <td>Verified (vendor statement)</td>
      </tr>
      <tr>
          <td>~400 environments are an exposure count, not compromise</td>
          <td>The Register</td>
          <td>Qualified (vendor statement as reported)</td>
      </tr>
      <tr>
          <td>CVE-2026-84869 description, CVSS 9.9, fixed in 26.6.5</td>
          <td><a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/84xxx/CVE-2026-84869.json">CVE record</a></td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>CVE-2026-84869 added to KEV on Sep 11, 2026</td>
          <td><a href="https://www.cisa.gov/known-exploited-vulnerabilities-catalog">CISA KEV</a> (kev-data JSON)</td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>No attribution</td>
          <td>Huntress, CyberScoop</td>
          <td>Verified</td>
      </tr>
  </tbody>
</table>
]]></content:encoded></item><item><title>N-able N-central Offline After Able2Shell Zero-Days</title><link>https://firewallsync.com/posts/n-able-n-central-able2shell-zero-days-offline-what-we-know/</link><guid>https://firewallsync.com/posts/n-able-n-central-able2shell-zero-days-offline-what-we-know/</guid><pubDate>Wed, 11 Nov 2026 04:56:00 +0000</pubDate><dc:creator>Craig Leslie</dc:creator><category>Security Operations</category><description>A researcher published exploit code for what Huntress counts as 33 critical N-able N-central flaws on November 8. N-able took hosted N-central offline, told on-premises customers to shut their servers down, and on November 10 published seven CVEs and a hotfix. What is confirmed, what is not, and what MSPs and IT teams should check.</description><enclosure url="https://firewallsync.com/posts/n-able-n-central-able2shell-zero-days-offline-what-we-know/cover_hu17160248664421550311.jpg" type="image/jpeg" length="0"/><media:content url="https://firewallsync.com/posts/n-able-n-central-able2shell-zero-days-offline-what-we-know/cover_hu17160248664421550311.jpg" medium="image" type="image/jpeg" width="1200" height="630"/><content:encoded><![CDATA[<p><img src="https://firewallsync.com/posts/n-able-n-central-able2shell-zero-days-offline-what-we-know/cover_hu17160248664421550311.jpg" alt="A long aisle between rows of open grey metal equipment cabinets under a steel-truss warehouse roof" width="1200" height="630"></p><p><em>Reported as of November 11, 2026, 05:00 UTC. We will add dated updates here if confirmed facts change.</em></p>
<p>N-able has taken its <strong>cloud-hosted N-central</strong> service offline and told customers who run N-central on their own servers to <strong>shut them down</strong>, after an independent researcher published exploit code for dozens of unpatched flaws on Sunday, November 8. N-central is a remote monitoring and management (RMM) platform: managed service providers (MSPs) and IT teams use it to push scripts, patches and remote sessions to the machines they manage, which is why a takeover of the server can reach every downstream customer.</p>
<p>On November 10 N-able published <strong>seven CVE records</strong> and, per <a href="https://www.csoonline.com/article/4247028/n-able-n-central-gets-emergency-fix-two-days-after-33-exploits-published.html">CSO Online</a>, an emergency hotfix. N-able says it has <strong>no evidence of successful exploitation</strong> of customer environments. Below: what is confirmed, what is not, and what to check if N-central is in your environment.</p>
<h2 id="timeline">Timeline</h2>
<table>
  <thead>
      <tr>
          <th>Date (2026)</th>
          <th>Event</th>
          <th>Source</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Aug 3 to Sep 8</td>
          <td>Three earlier N-central flaws added to CISA&rsquo;s Known Exploited Vulnerabilities (KEV) catalog: CVE-2026-18577, CVE-2026-18556, CVE-2026-86218</td>
          <td><a href="https://github.com/cisagov/kev-data">CISA KEV data</a></td>
      </tr>
      <tr>
          <td>Sun Nov 8</td>
          <td>Researcher publishes &ldquo;Able2Shell&rdquo; exploit chains on GitHub</td>
          <td><a href="https://techcrunch.com/2026/11/10/n-able-takes-its-remote-access-service-offline-after-researcher-publishes-dozens-of-zero-day-bugs/">TechCrunch</a></td>
      </tr>
      <tr>
          <td>Nov 9</td>
          <td>N-able takes hosted N-central offline; says no active exploitation seen as of 15:15 UTC; tells customers to keep servers offline until it confirms they can be restored</td>
          <td><a href="https://www.huntress.com/blog/n-able-disables-cloud-services-following-disclosure-of-able2shell-exploit-chains">Huntress</a>, <a href="https://cybersecuritynews.com/n-able-takes-n-central-servers-offline/">Cybersecurity News</a></td>
      </tr>
      <tr>
          <td>Nov 9 to 10</td>
          <td>watchTowr reports exploitation attempts against N-central honeypots; Defused reports probing</td>
          <td><a href="https://cybersecuritynews.com/n-able-takes-n-central-servers-offline/">Cybersecurity News</a></td>
      </tr>
      <tr>
          <td>Nov 10</td>
          <td>N-able publishes seven CVE records; hotfix N-central 2026.4 HF2 reported</td>
          <td>CVE records (below), <a href="https://www.csoonline.com/article/4247028/n-able-n-central-gets-emergency-fix-two-days-after-33-exploits-published.html">CSO Online</a></td>
      </tr>
  </tbody>
</table>
<h2 id="confirmed-vs-not-confirmed">Confirmed vs not confirmed</h2>
<table>
  <thead>
      <tr>
          <th>Claim</th>
          <th>Status</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Hosted N-central taken offline by N-able</td>
          <td><strong>Confirmed</strong> by N-able&rsquo;s status page, as quoted by TechCrunch</td>
      </tr>
      <tr>
          <td>On-premises customers told to take servers offline</td>
          <td><strong>Confirmed</strong>: N-able guidance reported by Huntress, TechCrunch and CSO Online</td>
      </tr>
      <tr>
          <td>Seven CVEs, affected versions before 26.4.1</td>
          <td><strong>Confirmed</strong> in N-able&rsquo;s own CVE records</td>
      </tr>
      <tr>
          <td>33 vulnerabilities in four chains</td>
          <td><strong>Researcher&rsquo;s count</strong>, as summarised by Huntress; N-able has not said how many it reproduced (CSO Online)</td>
      </tr>
      <tr>
          <td>Exploitation of customer environments</td>
          <td><strong>Not confirmed</strong>: N-able says it has no evidence of successful exploitation</td>
      </tr>
      <tr>
          <td>Exploitation attempts against internet-facing N-central</td>
          <td><strong>Reported</strong> by watchTowr (honeypots) and Defused (probing), via Cybersecurity News</td>
      </tr>
      <tr>
          <td>Hosted service restored</td>
          <td><strong>Not confirmed</strong> by us at the time of writing</td>
      </tr>
  </tbody>
</table>
<h3 id="why-the-researcher-published">Why the researcher published</h3>
<p>TechCrunch reports the researcher told BleepingComputer he released the exploits because N-able allegedly failed to patch flaws he had reported in a different product. That is his account; we have not seen N-able respond to it.</p>
<h2 id="the-seven-cves">The seven CVEs</h2>
<p>All seven records were published on November 10, 2026 by N-able as the CVE Numbering Authority, with CVSS v4.0 scores from N-able. We read them from the <a href="https://github.com/CVEProject/cvelistV5">CVE Program&rsquo;s cvelistV5 repository</a>.</p>
<table>
  <thead>
      <tr>
          <th>CVE</th>
          <th>Title (as published)</th>
          <th>CWE</th>
          <th>CVSS v4</th>
          <th>Privileges required</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>CVE-2026-125883</td>
          <td>Multiple XXE Vulnerabilities</td>
          <td>CWE-611</td>
          <td>9.3 Critical</td>
          <td>None</td>
      </tr>
      <tr>
          <td>CVE-2026-125881</td>
          <td>Schema-hint SSRF via service import schema validation</td>
          <td>CWE-918</td>
          <td>9.3 Critical</td>
          <td>None</td>
      </tr>
      <tr>
          <td>CVE-2026-125878</td>
          <td>Multiple OGNL Injection vulnerabilities</td>
          <td>CWE-79</td>
          <td>8.7 High</td>
          <td>Low</td>
      </tr>
      <tr>
          <td>CVE-2026-125879</td>
          <td>Local privilege escalation to root via nable-writable syslog-ng config</td>
          <td>CWE-266</td>
          <td>8.6 High</td>
          <td>High</td>
      </tr>
      <tr>
          <td>CVE-2026-125882</td>
          <td>RCE via file repository upload path traversal</td>
          <td>CWE-23</td>
          <td>8.6 High</td>
          <td>High</td>
      </tr>
      <tr>
          <td>CVE-2026-91000</td>
          <td>Insecure IPC Channels lead to local privilege escalation</td>
          <td>CWE-306</td>
          <td>8.4 High</td>
          <td>Low (local)</td>
      </tr>
      <tr>
          <td>CVE-2026-125880</td>
          <td>Stored XSS via MMS3 patch metadata (admin context)</td>
          <td>CWE-644</td>
          <td>8.3 High</td>
          <td>High</td>
      </tr>
  </tbody>
</table>
<p>Two details worth noticing if you automate on CVE data:</p>
<ul>
<li>Six records say &ldquo;before <strong>26.4.1</strong>&rdquo;; CVE-2026-91000 says &ldquo;before <strong>2026.4.1</strong>&rdquo;, both with <code>versionType</code> <code>custom</code>. The product&rsquo;s own builds are named like 2026.4.0.31, and the hotfix is reported as &ldquo;2026.4 HF2&rdquo;. A naive version comparison can mis-handle that mix; our guide to <a href="/posts/cve-affected-versions-lessthan-defaultstatus-versiontype/">CVE affected versions, lessThan and versionType</a> explains why <code>custom</code> ranges need a human check.</li>
<li>CVE-2026-125878 is titled OGNL injection but carries CWE-79 (cross-site scripting). That is how N-able filed it; it may be corrected later.</li>
</ul>
<p>None of the seven is in CISA&rsquo;s KEV catalog as of catalog version 2026.11.10 (released November 10, 19:03 UTC). Five older N-central CVEs are, the three from 2026 listed above plus CVE-2025-8875 and CVE-2025-8876. If you watch the feed, our <a href="/posts/cisa-kev-json-feed-what-each-field-means-and-how-to-match-it-against-a-scanner-export/">KEV JSON field guide</a> shows how to match it against your inventory.</p>
<h2 id="how-the-attack-works-as-far-as-sources-say">How the attack works (as far as sources say)</h2>
<p>Huntress describes four chains: three end in remote code execution on the N-central server and one escalates to root. Cybersecurity News notes one public proof of concept chains an XXE flaw into unauthenticated remote code execution. The CVE records confirm two flaws exploitable over the network with no privileges (XXE and SSRF, both 9.3) and two local paths to root (syslog-ng config and insecure IPC).</p>
<p>The exposure matters because of what N-central does. An attacker who controls the server can use it as designed: open remote sessions, deploy scripts and create administrator accounts across managed endpoints. Huntress&rsquo;s guidance focuses on exactly those downstream actions.</p>
<h2 id="what-to-check-in-your-environment">What to check in your environment</h2>
<p>From Huntress, N-able&rsquo;s guidance as reported, and the CVE records:</p>
<ol>
<li><strong>On-premises N-central: keep it offline until you can patch.</strong> Then apply the hotfix and, per CSO Online, upgrade Agents and Probes as well, or they will lose compatibility with the server.</li>
<li><strong>Review authentication from November 8 onward.</strong> Huntress recommends checking login and authentication activity for unauthorized access, and involving incident response if you find any.</li>
<li><strong>Look downstream.</strong> Anomalous remote access sessions, newly deployed scripts, and new administrator accounts on N-central and on managed endpoints.</li>
<li><strong>Check exposure.</strong> If your N-central console was reachable from the internet between November 8 and patching, treat the probing reported by watchTowr and Defused as relevant to you.</li>
<li><strong>Hosted customers:</strong> follow N-able&rsquo;s status page; you cannot patch the hosted service yourself. Plan for how you will reach managed endpoints without your RMM during the outage.</li>
</ol>
<p>For a broader take on deciding what to patch first when several signals compete, see our <a href="/posts/vulnerability-prioritization-workflow-cve-record-to-patch-ticket/">vulnerability prioritization workflow</a>. Here the decision is easier than most: a public exploit, unauthenticated network flaws and a tool with administrative reach over every managed machine.</p>
<h2 id="what-is-not-known-yet">What is not known yet</h2>
<ul>
<li>Whether any customer environment was compromised. N-able&rsquo;s statement is &ldquo;no evidence&rdquo;, and it has not said what logging that conclusion rests on.</li>
<li>How many of the 33 published issues the hotfix addresses; seven CVEs were assigned.</li>
<li>When hosted N-central will be fully restored.</li>
</ul>
<h2 id="sources-and-verification">Sources and verification</h2>
<table>
  <thead>
      <tr>
          <th>Important claim</th>
          <th>Source</th>
          <th>Status</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Hosted N-central offline; N-able status page wording; &ldquo;no evidence of successful exploitation&rdquo;; on-prem customers told to go offline</td>
          <td><a href="https://techcrunch.com/2026/11/10/n-able-takes-its-remote-access-service-offline-after-researcher-publishes-dozens-of-zero-day-bugs/">TechCrunch, Nov 10</a></td>
          <td>Verified (N-able status page quoted; we could not load the page directly)</td>
      </tr>
      <tr>
          <td>33 vulnerabilities, four chains, build 2026.4.0.31, no active exploitation as of Nov 9 15:15 UTC, review guidance</td>
          <td><a href="https://www.huntress.com/blog/n-able-disables-cloud-services-following-disclosure-of-able2shell-exploit-chains">Huntress, Nov 9</a></td>
          <td>Verified; count is the researcher&rsquo;s</td>
      </tr>
      <tr>
          <td>Hotfix 2026.4 HF2; agents and probes must be upgraded; N-able has not confirmed how many flaws it reproduced</td>
          <td><a href="https://www.csoonline.com/article/4247028/n-able-n-central-gets-emergency-fix-two-days-after-33-exploits-published.html">CSO Online, Nov 10</a></td>
          <td>Qualified: trade press, not an N-able document we could read</td>
      </tr>
      <tr>
          <td>watchTowr honeypot exploitation attempts; Defused probing</td>
          <td><a href="https://cybersecuritynews.com/n-able-takes-n-central-servers-offline/">Cybersecurity News, Nov 10</a></td>
          <td>Qualified: secondary report of vendor statements</td>
      </tr>
      <tr>
          <td>Seven CVEs, titles, CWEs, CVSS v4, affected ranges</td>
          <td>N-able CVE records in <a href="https://github.com/CVEProject/cvelistV5">cvelistV5</a>, e.g. <a href="https://www.cve.org/CVERecord?id=CVE-2026-125883">CVE-2026-125883</a></td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>Older N-central KEV entries; new CVEs not in KEV</td>
          <td><a href="https://www.cisa.gov/known-exploited-vulnerabilities-catalog">CISA KEV catalog</a>, version 2026.11.10</td>
          <td>Verified</td>
      </tr>
  </tbody>
</table>
]]></content:encoded></item></channel></rss>