Your MSP's Remote Management Tools Are Being Weaponised Right Now
The intelligence picture this week has a clear centre of gravity. It is not the Oracle Critical Patch Update, though that is substantial. It is the confirmed, ongoing exploitation of the remote management infrastructure that underpins how most UK small businesses receive IT support.
Two platforms. Both under active attack. Both patched in the last 48 hours. And neither patch does anything for businesses whose MSPs have not yet applied it.
Let us go through what the data shows, without embellishment.
Story One: ConnectWise ScreenConnect and the SCKit Toolkit
On the 17th of November 2026, ConnectWise confirmed it had completed its investigation into unauthorised access targeting partner ScreenConnect environments. The company disabled five ScreenConnect extensions across approximately 400 partner environments as a containment measure.
The recommendation from ConnectWise is specific: ensure the technician client is running the latest version. What the company is not broadcasting loudly enough is what the attacker activity looks like in practice.
A toolkit called SCKit is being used to systematically identify and exploit unpatched ScreenConnect on-premises installations. This is not opportunistic scanning. This is targeted tooling built specifically for this vulnerability surface. Someone built infrastructure around the premise that a meaningful number of MSP environments would remain unpatched long enough to be worth automating.
They were right.
For a UK small business, here is the translation: ScreenConnect is remote desktop software. It is what your IT support person uses when they say “let me just take a look at your screen.” If the version running on your MSP’s infrastructure is unpatched, an attacker with the SCKit toolkit can use that same access channel. Not to look at your screen. To move through your network, exfiltrate data, or deploy ransomware.
The supply chain attack model is not abstract here. It is the specific mechanism being exploited. The attacker does not need to compromise your business directly. They compromise the tool that already has trusted access to it.
Story Two: N-able N-central and Active Exploitation of Earlier Bugs
On the same date, N-able released N-central 2026.4 Hotfix 3, described by the company as a critical security update. It patches 17 vulnerabilities.
The detail that matters most: the reason this update is urgent is not the 17 new patches. It is that attackers were already exploiting earlier bugs in N-central, and using that access to deploy cryptocurrency miners on client systems.
Crypto miners are, in the threat intelligence hierarchy, the relatively polite end of what attackers deploy when they have persistent access to managed environments. They consume your computing resources. They drive up electricity costs. They degrade system performance. But they are also a signal: if an attacker had access deep enough to run a miner, they had access deep enough to run ransomware. The choice to deploy a miner rather than ransomware is their operational decision, not a constraint.
N-able’s Hotfix 3 removes legacy APIs and urges customers to upgrade their Agent and Probe components. This is not optional maintenance. These are the components that sit on client machines, maintaining the management channel between your systems and your MSP’s platform.
If your MSP uses N-central and has not applied Hotfix 3, those components on your machines remain vulnerable to the exploitation chain that was already being used before this patch existed.
The KEV Entry You Should Also Know About: Puppet Enterprise
CISA added CVE-2026-115731 to its Known Exploited Vulnerabilities catalogue on the 17th of November 2026. This is the authoritative list of vulnerabilities confirmed to be actively exploited in the wild. When something appears here, the question of whether exploitation is theoretical is settled.
The vulnerability is in Perforce Puppet Enterprise, specifically in Puppet’s report-processing code. The technical detail is this: a client with any certificate signed by the Puppet Certificate Authority can submit a crafted report via a PUT request, and that report executes arbitrary code on the Puppet Server as the service user.
Puppet Enterprise is configuration management software. It is used to automate the setup, maintenance, and configuration of servers. Larger MSPs and businesses with more complex IT infrastructure use it to ensure systems are consistently configured. If your MSP uses Puppet to manage your server environment, and if their Puppet infrastructure has not been patched, an attacker who can obtain a CA-signed certificate can run code on the system that manages your servers.
The CISA advisory notes a specific aggravating factor: if the certificate authority automatically signs requests without strong verification, an unauthenticated network attacker can obtain a valid certificate before exploiting the vulnerability. That is a known misconfiguration in some Puppet deployments.
Required action per CISA: apply vendor mitigations in accordance with BOD 26-04 guidance, or discontinue use of the product if mitigations are unavailable.
Why the Oracle Critical Patch Update Is Secondary Today
The NVD published a substantial batch of critical Oracle vulnerabilities on the 17th of November 2026. Multiple CVEs scored at CVSS 10.0 across Oracle Access Manager, Oracle WebLogic Server, Oracle Business Intelligence Enterprise Edition, and Oracle Fusion Middleware. Several additional vulnerabilities scored 9.9 across Oracle Database Server and Oracle Hyperion products.
These are genuinely severe. Unauthenticated remote code execution against identity management infrastructure is not a minor finding.
However, for the audience that matters here: UK small businesses running 5 to 50 people. The honest assessment is that direct Oracle middleware exposure is uncommon at this scale. Oracle Business Intelligence and Oracle Access Manager are enterprise-tier products. If your business uses them directly, your IT team already knows about this patch cycle.
The MSP angle is different. Some MSPs run Oracle infrastructure on the backend. If yours does, the question is worth asking. But for most readers of this analysis, the ScreenConnect and N-central stories carry more direct operational relevance today.
How to Turn This Into a Competitive Advantage
Businesses that ask their MSP informed questions about patching status and get documented answers are, statistically, better protected than businesses that do not. That is not a complicated observation, but it has a practical implication.
If you are able to request written confirmation that your MSP’s remote management tools are patched, and if you can show that confirmation to a prospective client or partner who asks about your security posture, you have demonstrated something most businesses your size cannot: active, documented oversight of your supply chain.
Cyber Essentials, which the NCSC administers, includes supply chain security in its scope considerations. Demonstrating that you actively monitor and verify your MSP’s patching status is a defensible, auditable position. It costs nothing except the time to send two emails.
Making the Case Internally
If you need to escalate this within your organisation, here are the arguments that hold weight:
The access is already there. Your MSP’s remote tools have privileged access to your systems by design. The question is not whether that access exists, it is whether it is being defended. Unpatched remote management software is an open door with a trusted key already in the lock.
Exploitation is confirmed, not theoretical. CISA’s Known Exploited Vulnerabilities catalogue is not a research list. It is confirmed in-the-wild exploitation. When CISA adds a CVE, it means someone has already used it against a real target. That target may have been an MSP that serves businesses like yours.
The cost of asking is zero. Sending your MSP an email asking for patch confirmation costs nothing. The cost of not asking, if your environment is subsequently compromised via their infrastructure, is a GDPR breach notification, potential ICO enforcement, client notification obligations, and recovery costs that routinely run into five and six figures for businesses of this size.
Insurance implications are real. Cyber insurance underwriters increasingly ask whether businesses exercise oversight of their IT suppliers. Documented evidence that you asked and received answers strengthens your position both in policy negotiations and in the event of a claim.
What to Do Before the End of the Week
1. Email your MSP today with three specific questions.
Ask: Which remote management and monitoring tools do you use to access and manage our systems? Have you applied the latest patches to ConnectWise ScreenConnect and N-able N-central? Can you confirm in writing the current patch status of these tools and the date the updates were applied?
Document the response. If the response is evasive or incomplete, that is itself diagnostic information.
2. Ask specifically about Puppet Enterprise if you have server infrastructure.
If your MSP manages servers on your behalf, ask whether they use Puppet Enterprise for configuration management and whether CVE-2026-115731 has been remediated. This is on CISA’s actively-exploited list. It warrants a direct question.
3. Check for indicators on your own systems.
If you have access to your systems’ event logs or your MSP provides a monitoring dashboard, look for: unexpected outbound connections, new scheduled tasks or services you did not authorise, unusual CPU or memory usage that might indicate a crypto miner, and any remote sessions outside your normal business hours. You do not need to be a technical expert to notice that something looks unusual and ask your MSP to explain it.
4. Establish a patching confirmation cadence.
Ask your MSP to provide monthly written confirmation that their management tools are patched to current versions. If they are a competent provider, this takes them five minutes to produce. If they resist or cannot produce it, you have learned something important about the quality of their internal processes.
5. Review your incident response contact list.
If your MSP’s infrastructure were compromised and your systems were affected, do you know who to call? Do you have a direct contact at your MSP beyond the helpdesk ticket queue? Do you have your cyber insurance policy details accessible? Make sure these are written down and accessible to more than one person in your business.
This episode’s companion article covers three stories: the ScreenConnect and N-central MSP exploitation campaigns, the Puppet Enterprise KEV addition, and a summary assessment of the Oracle Critical Patch Update for small business readers. All sources are linked in the table below.
If this was useful, please follow the show wherever you listen. A rating or review helps others find it. Leave a comment with your thoughts, particularly if you have asked your MSP these questions and want to share what you heard back. And if you know a business owner who relies on managed IT services and has never thought about this risk, send them this episode. It is exactly the kind of thing worth passing on.