Skip to main content
Black Friday: 40% off your first 3 months on any monthly plan with code BF40. Ends Dec 2.See the offer
Varaxon Technologies

Prioritization

RMM and remote access tools on CISA's KEV list in 2026

Ten CVEs in RMM and remote support tools joined CISA's KEV list in 2026. Which products, how long agencies had to fix them, and what EPSS said the day before.

By Brandon Sooknanan, Founder, Varaxon Technologies · · 5 min read

Remote monitoring and management (RMM) and remote support tools are built to reach every machine a team looks after. That is what makes them valuable to an MSP or an IT department, and it is also why a flaw in one is worth so much to an attacker: one way in can lead to every client or every endpoint behind it.

This page counts the CVEs in those tools that CISA added to its Known Exploited Vulnerabilities (KEV) catalog between 1 January and 17 November 2026. KEV only lists vulnerabilities with reliable evidence of exploitation, so every entry below is one attackers have used, not a theoretical risk. We counted from CISA's KEV feed (catalog version 2026.11.17) and FIRST's EPSS scores, and we will update the page when new entries appear.

The 10 entries added in 2026

RMM and remote support CVEs added to CISA KEV in 2026 (catalog 2026.11.17). Ransomware = CISA's knownRansomwareCampaignUse field. EPSS = score the day before the KEV listing.
Added to KEVCVEProductWeakness (CISA's name)Fix windowRansomwareEPSS day before
13 FebCVE-2026-1731BeyondTrust Remote Support and Privileged Remote AccessOS command injection3 daysKnown4.2%
24 AprCVE-2024-57726SimpleHelpMissing authorization14 daysKnown0.3%
24 AprCVE-2024-57728SimpleHelpPath traversal14 daysKnown1.2%
28 AprCVE-2024-1708ConnectWise ScreenConnectPath traversal14 daysKnown51.7%
29 JunCVE-2026-48558SimpleHelpAuthentication bypass3 daysUnknown0.7%
3 AugCVE-2026-18577N-able N-centralAuthentication bypass (alternate path)3 daysUnknownNo score
4 AugCVE-2026-18556N-able N-centralAuthentication bypass (alternate path)3 daysUnknown0.3%
8 SepCVE-2026-86218N-able N-centralStatic code injection3 daysUnknown0.4%
11 SepCVE-2026-84869ConnectWise ScreenConnectImproper privilege management and missing authorization3 daysUnknown0.4%
16 OctCVE-2026-102764BeyondTrust Remote SupportAuthentication bypass by spoofing3 daysUnknownNo score

The fix window is the gap between the date CISA added the CVE and the due date in its catalog entry. That deadline binds US federal civilian agencies, but it is also the most useful public benchmark for everyone else. Three of the 10 are 2024 CVEs that CISA added this year, a reminder that the year in a CVE number says nothing about whether it is being exploited now.

What the list shows

  • Getting in without a password is the common thread. Six of the 10 are authentication bypass or missing authorization flaws. For a tool that already has administrative reach into every managed machine, skipping the login is often all an attacker needs.
  • Deadlines are now measured in days. Seven of the 10 had a 3-day fix window. Across all 298 CVEs CISA added in 2026, 161 had a fix window of 3 days or less. The October 2026 KEV report tracks how quickly that has changed.
  • Ransomware links are already on record for four. CISA marks the BeyondTrust command injection, both 2024 SimpleHelp flaws and the 2024 ScreenConnect path traversal as known to be used in ransomware campaigns.
  • The same products come back. N-central has three entries this year and SimpleHelp three. A product with one KEV entry is a good place to check first when the next advisory lands.

EPSS did not see most of these coming

EPSS estimates the probability that a CVE will be exploited in the next 30 days. It is a useful way to rank findings that are not on KEV, but it is a prediction, and it often lags behind events. For nine of these 10 CVEs, the EPSS score on the day before CISA listed them was under 10% or did not exist yet. The one exception, ScreenConnect CVE-2024-1708 at 51.7%, was a 2024 CVE that had been public for more than two years.

That matches the pattern across the whole catalog: 81% of the CVEs CISA added to KEV in 2026 had no EPSS score, or one under 10%, the day before they were listed. For remote access tools, the practical rule is simpler: treat a new critical advisory as urgent on the day it is published, and do not wait for a score to rise.

What to do with this

  1. Know where these tools run. Keep a list of every RMM, remote support and remote access product in use, for your own team and each client, including old installs nobody uses any more. A forgotten SimpleHelp or ScreenConnect server can't be patched if nobody knows it exists.
  2. Watch the vendors' security pages and the KEV feed. A new KEV entry for a product on your list is a same-day job. Tracking KEV and EPSS with curl and jq shows a free way to check daily.
  3. Keep management consoles off the open internet where the product allows it, and put the rest behind a VPN or an allow list.
  4. Confirm the fix on every component. Some fixes must reach agents and probes as well as the server. A rescan or an inventory pull that lists versions is the evidence; a closed ticket is not.
  5. Check for signs of earlier access. Patching closes the hole. It does not show whether someone used it first, so follow the vendor's guidance on what to look for.

Varaxon Scan Hub puts KEV status, ransomware use and EPSS next to every finding in the scans you already run, ranks findings on CISA's KEV list first, and shows on the next rescan whether each one is really gone. See a sample report.

Common questions

Which RMM and remote access tools are on CISA's KEV list in 2026?

Between 1 January and 17 November 2026, CISA added 10 CVEs in these tools: three in N-able N-central, three in SimpleHelp, two in ConnectWise ScreenConnect and two in BeyondTrust Remote Support and Privileged Remote Access.

Why are RMM tools targeted so often?

They are designed to run commands on many machines from one place. An attacker who gets into an RMM or remote support server can often reach every endpoint, and for an MSP every client, that it manages.

How fast should an MSP patch a remote access tool on the KEV list?

Treat it as a same-day job. Most of this year's entries gave US federal agencies three days, and attackers had already used each flaw before it was listed.

Turn your next scan export into a client-ready report.

Run a free pre-flight check

Cookie preferences

Essential site functions remain available whichever option you choose. Your advertising choice is saved on this site. The Scan Hub has a separate choice.

Google and Reddit may receive cookies, identifiers, browser and device information, and your network/IP information. Reject or withdraw at any time. Read the Privacy Policy.