Latest / Decrypted: The UK Cyber Briefing / The N-central patch that missed its own vulnerability, and the MSPs left exposed twice
Transcript
- 0:03This is Decrypted. Wednesday, the fifth of August.
- 0:06The N-central patch that missed its own vulnerability, and the MSPs left exposed twice.
- 0:12N-able patched an authentication bypass in its N-central remote monitoring platform some weeks back.
- 0:19It's the kind of fix that barely makes a changelog.
- 0:23Then, on 1 August, it discovered the patch had missed the actual hole.
- 0:28Attackers were already through it.
- 0:30They used N-central's own "Take Control" feature to reach into the networks of the businesses N-central is me
- 0:37ant to protect. Then they planted a Cloudflare Tunnel, so they could let themselves back in even after the doo
- 0:44r was properly shut.
- 0:49The next day, the US Cybersecurity and Infrastructure Security Agency added the incomplete-patch flaw to its
- 0:57Known Exploited Vulnerabilities catalogue, with a deadline of 6 August for federal agencies.
- 1:03A day after that, it added the original flaw too.
- 1:06Two entries, one product, four days.
- 1:10N-central is remote monitoring and management software, or R M M.
- 1:15It's the tool thousands of managed service providers use to watch over other people's networks.
- 1:21Which means this was never really N-able's problem alone.
- 1:24Next. A lock changed, a window left open.
- 1:29The original flaw is C V E twenty twenty-six, one eight five five six.
- 1:35It let an unauthenticated attacker reach administrator-level control of an N-central server through an altern
- 1:42ate path. It affected every version up to 2026.
- 1:471. N-able fixed it in version 2026.
- 1:512.
- 1:55A second path, catalogued separately as C V E twenty twenty-six, one eight five seven seven, stayed open in e
- 2:04very build up to 2026.3.1.
- 2:087.
- 2:12It says only that the discovery followed unusual licensing errors from on-premises deployments.
- 2:18In hindsight, that stray signal was attackers moving around inside the platform.
- 2:23Exploitation of the second path began on 1 August, before the real fix shipped.
- 2:29And here's the part that should worry you.
- 2:31The security firm Huntress found that among the servers it could see, more than half remained unpatched even
- 2:39after the fix was available.
- 2:40Publishing a patch and applying one are different events.
- 2:44Attackers live in the gap between them.
- 2:46And finally. The Secure by Design lesson.
- 2:50The specific bug matters less than the shape of the failure.
- 2:54A patch that closes the named C V E without closing the underlying weakness isn't a fix.
- 3:00It's a delay.
- 3:03Before shipping a security patch, a vendor shouldn't just ask, "does this stop the reported exploit?
- 3:10" They should ask, "does this remove the class of weakness?
- 3:13" And they should check it against variant attempts, not just the original proof of concept.
- 3:19For UK organisations, the lesson sits one level up.
- 3:23That's especially true for smaller ones that outsource I T to a managed service provider precisely so they do
- 3:30n't have to think about this.
- 3:31An R M M platform is designed to be a single point of access into many customers' networks.
- 3:37That's the product.
- 3:41Does it ask which of your suppliers can reach into your network the way N-central reaches into an M S P's cus
- 3:47tomers? If it doesn't, it has a blind spot exactly this shape.
- 3:52It's worth asking your provider three things.
- 3:55Which platform do they run?
- 3:57Does it face the internet?
- 3:58And how fast do they apply hotfixes, rather than waiting for the next scheduled update?
- 4:04That was Decrypted. The written version and every source are linked in the show notes.
- 4:09Thanks for listening.