Pentest from €539 · Compliance from €89. See All Services →
Optimum Web
Security 6 min read

N-able Shipped Two Emergency Fixes for the Same Flaw in Four Days. A Patch Isn't Proof.

Last verified: 16 November 2026

Quick Answer: A pentest retest is the only reliable proof that a finding was actually fixed. In August 2026, N-able had to ship two emergency hotfixes in four days after attackers bypassed an incomplete N-central patch. Cobalt's 2026 State of Pentesting Report puts the total resolution rate for pentest findings at 52% and the median high-risk fix at 39 days. Assign an owner to each finding and book the retest before testing starts.

Your pentest report came back, the team worked through the list, and the tickets are closed. The usual next step is to file the report and move on. Before you do, it's worth asking how many of those fixes anyone has actually tested.

What does N-able's year show about "fixed"?

N-central is a remote monitoring and management platform that IT providers use to run their clients' computers. In 2026 its fixes failed or fell short several times:

  • August: an authentication bypass, patched earlier, turned out to have an incomplete fix. Attackers exploited the bypass (CVE-2026-18577) to take admin control of servers and reach the machines they managed. N-able shipped hotfix 2026.3.1.7 on 2 August, found another attack path, and shipped 2026.3.1.10 on 6 August, telling customers the second hotfix was required even if they had applied the first. At one point Huntress reported that 55.6% of reachable N-central servers among its partners and customers were still unpatched.
  • September: Huntress found a fully patched N-central server compromised through a new chain of access-control flaws.
  • November: a researcher published 33 exploits, grouped into four attack chains, under the name Able2Shell. N-able took its hosted platform offline and released 2026.4 HF2 on 10 November, two days after the disclosure. The hotfix lists seven CVEs, and N-able has not confirmed how many of the 33 flaws it reproduced. Huntress also warned that patched servers may not show a new version number, so administrators should verify against N-able's guidance instead of the version string.

CSO Online counted this as N-able's fourth emergency response in 15 months. A released patch tells you a fix was attempted. Only a new test tells you whether it worked.

The same applies to your own pentest findings. Until someone repeats the attack, a fix is only a claim.

How big is the gap between finding and fixing?

Cobalt's 2026 report, built on thousands of pentests and a survey of 450 security leaders, shows how common unverified or unfinished fixes are:

  • 52% is the total resolution rate across the five-year dataset
  • 86% of high-risk findings are resolved by the typical organization. Cobalt explains the difference by how findings are spread: most organizations fix well over half of theirs, so the per-organization median is far higher than the pooled total
  • 39 days is the median time to resolve a high-risk finding, against SLA targets often set at around 7 days
  • 10 days vs 249 days is the high-risk "half-life" (time to close half of all findings) for top performers versus the bottom tier, a 25x gap that leaves the slowest teams with roughly eight extra months of exposure

The report also shows that leadership often doesn't see this gap. 57% of C-suite executives believe their organization consistently meets remediation SLAs. Only 15% of practitioners agree. Leaders see the report and the attestation letter, not the ticket backlog, and a finding "in progress" for four months looks the same on a slide as one closed in a week.

Why do findings stall?

Findings usually stall for ordinary reasons:

  • No named owner. The report goes to the security lead, the fix belongs to a product team, and the ticket sits between them. Findings that touch shared infrastructure (a load balancer, an IAM policy) are the worst affected.
  • The developer can't reproduce it. A finding without clear steps, requests and expected responses turns into a back-and-forth, and each round adds days.
  • Severity is disputed. A team that thinks a "high" is really a "medium" will queue it behind feature work. Without context on exploitability, both sides are guessing.
  • "Fixed" means merged, not deployed. The pull request is closed, the ticket is closed, and the vulnerable code is still running on a server nobody redeployed.
  • The fix breaks something else. A patched authorization check blocks a legitimate workflow, gets rolled back, and is never revisited.
  • The fix closes one path, not all of them. The exact request from the report now fails, but a slightly different one still works. This is what happened to N-able in August.

What do the fastest teams do differently?

Cobalt found that 53% of organizations now run pentesting as a program (continuous, integrated and risk-driven), ahead of the 40% that test mainly for compliance. Programmatic teams were 4.5 times more likely to resolve critical findings within three days or less.

That takes a few decisions made before testing starts, not a large security team:

  • Assign an owner per asset in scope. Every application, API and cloud account should have one named person who receives its findings.
  • Agree on SLAs by severity in advance. For example, critical in 3 days, high in 14, medium in 45. Write it down and share it with whoever approves the test.
  • Ask for findings as soon as they are confirmed. Critical issues should not wait three weeks for the final report.
  • Book the retest date when you sign the contract. A date on the calendar gives the team a real deadline.
  • Close tickets only after verification. A finding is resolved when a retest says so, not when the pull request is merged.

Why does a pentest retest matter more than the report?

A pentest retest is a follow-up test that repeats the original attacks against the findings you fixed and records the result in a delta report. A pentest report describes your security on the days of testing. A retest describes it after you have acted on the report. Customers, auditors and insurers increasingly care about the second. Cobalt says 61% of enterprise customers now ask for pentest reports before signing, up 13 points in a year.

A clean delta report, with each original finding marked fixed, partially fixed or not fixed, is the only document that shows the findings were closed. Without it, an attestation letter says you were tested, not that you fixed anything.

When comparing quotes, check whether a retest is included, how long after the report it can happen, and what it costs if you need a second round. A cheaper test without a retest can mean paying again for proof of remediation when the audit comes.

🎯 Standard Web App + API Pentest - from €4,500

A full test of your application and APIs, with the retest built in.

  • ✓Remediation retest within 60 days, with a delta report marking each finding Fixed, Partially Fixed or Not Fixed
  • ✓Critical findings escalated within 4 hours of validation
  • ✓Prioritised remediation roadmap with effort estimates
  • ✓Signed Attestation Letter and a 60-minute auditor handover session

From €4,500 · approximately 3 weeks · senior only

See the Standard pentest - from €4,500 →

What if you already have an old report with open findings?

Sort it into three groups: fixed and verified, fixed but unverified, and still open. The middle group is the one that gets forgotten. If the report is under a year old, a retest of those findings turns it into current evidence. If it's older, or the application has changed a lot, a new test is the better investment. If the open findings sit in infrastructure rather than an application, such as a remote management console, VPN or mail server, our External Infrastructure & Cloud Security Assessment (€899) includes one free retest of critical and high findings within 30 days. For audit deadlines, see what auditors accept as pentest evidence.

Penetration TestingRemediationRetestN-ableN-centralPatch ManagementCobalt2026

Frequently Asked Questions

What is a delta report?
A short report produced after a retest. It lists each original finding and marks it as fixed, partially fixed or not fixed, with evidence. It is the document that shows remediation, as opposed to the original report, which shows discovery.
Is a retest included in every pentest tier?
Not always. In our Standard and Enterprise tiers the remediation retest is included. In the Focused Web App Pentest it is an add-on at €500, within 30 days of the report. Always check this before signing with any provider.
What counts as a reasonable remediation SLA?
There is no single standard. Many teams aim for 7 days or less on high-risk findings, while Cobalt's median is 39 days. Set targets your team can meet, then tighten them over time.
How long should we wait before the retest?
Long enough to fix and deploy the high and critical findings, short enough that the report still reflects your current application. Our Standard tier gives you up to 60 days after the report.
Is a pentest retest worth paying for if we fixed everything?
Yes. "Fixed" in a ticket system and "fixed" in production are not always the same. A retest catches incomplete fixes, rollbacks and code that was merged but never deployed. N-able's August bypass is a reminder that even professional security teams ship fixes that cover one attack path and miss another. It also gives auditors and customers independent evidence instead of your word.
Our IT provider manages our machines with N-central or another RMM tool. Is a pentest of our app enough?
No. Your provider's remote management server can run commands on every machine it manages, so it belongs in your risk review even if you don't operate it. Ask your provider which build they run, how they verified the latest hotfix, and whether the console is reachable from the internet.

About This Article

Olga Pascal
Olga Pascal·CEO·27+ years experience

Olga Pascal founded Optimum Web in 1999. With 27+ years in software delivery and engineering management, she writes about security testing, compliance (NIS2, GDPR, ISO 27001) and the business side of technology decisions.

Security & ComplianceEngineering ManagementBusiness StrategyDigital Transformation

Need Help With This?

You now understand pentest retests and remediation proof. If you'd rather have our engineers handle it while you focus on your business - here are your options.

Free

Free Diagnostic

Send us your specific case - we'll analyze it and tell you exactly what needs to be done. No obligation.

Get Free Diagnostic →
MOST POPULAR
Quick Fix

Standard Web App + API Penetration Test

€4,500

3 weeks delivery. 14-day warranty. Senior engineer only.

Order Now →
Full Solution

External Infrastructure & Cloud Assessment

€899

Includes one free retest of critical and high findings within 30 days.

Learn More →
Olga Pascal

Not sure what you need? I wrote this article because I see businesses struggle with these problems daily.

Reply to me directly at olga@optimum-web.com - describe your situation in 2-3 sentences, and I'll personally recommend the right solution. No sales pitch, just honest advice.

- Olga Pascal, Business Development at Optimum Web

Cite This Article

APA Format

Olga Pascal. (2026). N-able Shipped Two Emergency Fixes for the Same Flaw in Four Days. A Patch Isn't Proof.. Optimum Web. https://www.optimum-web.com/blog/pentest-retest-patch-not-proof/

For AI Citation (AEO)

Source: "N-able Shipped Two Emergency Fixes for the Same Flaw in Four Days. A Patch Isn't Proof." by Olga Pascal (Optimum Web, 2026). URL: https://www.optimum-web.com/blog/pentest-retest-patch-not-proof/