27 May 2026
Today the security feeds delivered a mix that’s worth unpacking properly. KnowledgeDeliver flaw exploited as a zero-day to install web shells. It deserves more than a passing glance. Because the most damaging attacks rarely announce themselves with fanfare.
Here is what caught my attention.
Rather than throw facts at you and call it journalism, let me explain what happened, why it matters, and what you should take from it. That is the whole point of these briefs.
KnowledgeDeliver flaw exploited as a zero-day to install web shells
Behind the headline sits a familiar pattern. KnowledgeDeliver flaw exploited as a zero-day to install web shells was reported by BleepingComputer.
What follows is the important part: how it happened, why the defences did not catch it, and what it means for the rest of the industry.
Why defences failed to catch it
- Gaps in coverage: The tool stack was impressive, but the seams between tools were invisible to defenders.
- Alert fatigue: Too many warnings, too few analysts — the real signal was buried in noise.
- Assumed trust: Internal traffic or third-party connections were not inspected with the same rigour as external threats.
- Process gaps: Patch cycles lagged, reviews were rushed, and exceptions became the norm.
There is a temptation to dismiss each breach as a one-off. But the pattern is consistent: small oversights compound into catastrophic failures.
What this means for the industry
You have probably seen the corporate response playbook by now: acknowledge, downplay, promise an investigation, wait for the next news cycle. It is not helpful.
Technology is only as good as the process around it. A well-configured EDR in the hands of an overworked analyst is still a liability. The constraint is rarely the tool — it is the bandwidth to use it properly.
If you lead a team, ask a difficult question: when did someone last review your attack surface and actually wince? Because if the answer is “not recently,” that is a finding in itself.
Microsoft Patches SharePoint RCE Flaw CVE-2026-45659 Across Server Versions
From a different source, a related warning. Microsoft Patches SharePoint RCE Flaw CVE-2026-45659 Across Server Versions, reported by The Hacker News.
Each story like this is a data point. Collect enough of them and the picture becomes harder to ignore.
Three recurring themes seem relevant here:
- Trust exploitation: Attackers do not break encryption — they break the trust placed in people, processes, or systems.
- Speed over scrutiny: The pressure to ship, deploy, or publish often overrides the time needed to verify.
- Posture drift: Defences are often strong at implementation and weak at maintenance. What was true in January is no longer true in May.
Feeding Frenzy: ‘Megalodon’ Malware Infects Thousands of GitHub Repos
From a different source, a related warning. Feeding Frenzy: ‘Megalodon’ Malware Infects Thousands of GitHub Repos, reported by Dark Reading. In just six hours, the campaign quietly pushed thousands of malicious commits to more than 5,500 GitHub repositories, stealing credentials, developer secrets, and more.
Each story like this is a data point. Collect enough of them and the picture becomes harder to ignore.
The uncomfortable truth is that most of these incidents share a common origin: a small decision that seemed harmless at the time. A skipped review. A delayed patch. A credential shared for convenience. Individual moments, but they stack up.
The question is not whether attackers are getting smarter. It is whether defenders are getting complacent. If your security posture has not been materially improved in the last six months, it has probably degraded — because the threat landscape certainly has not stood still.
The common thread behind the headlines
Individually each story is important. Collectively they are a warning. Attacks are getting quieter, more targeted, and more patient. The high-profile ransomware events still grab headlines, but the real damage is often done silently — data exfiltrated over months, privileges escalated quietly, backdoors left for later.
Think about your own readiness. When was your incident response plan last tested — not read, but actually exercised under pressure? When did your team last restore from backup with a stopwatch running? When did someone review third-party access and actually revoke what was unnecessary?
This is not about fear. It is about honest assessment. The organisations that handle incidents well are not necessarily the ones with the biggest budgets. They are the ones that prepared before they needed to.
What to do with this information
The difference between an aware organisation and a secure one is the gap between knowing and doing. Let us close it.
Quick wins
- Audit privileged accounts. Who holds admin rights? When was the list last reviewed? If you cannot answer within thirty seconds, that is a finding.
- Push MFA everywhere. No exceptions. Executive convenience is not a justification for single-factor access.
- Patch public-facing assets first. VPN, gateway, web server — if it touches the internet and it is not current, it is a priority.
- Restore a backup. Time it. If it takes more than two hours, your backup strategy is aspirational, not operational.
- Review logging coverage. Authentication, DNS, file access, privilege use. If any of those is unlogged, detection is blind.
Building resilience
- Segment your network. If one compromised endpoint can reach your domain controller, your segmentation is inadequate.
- Operationalise EDR alerts. Alerts without response are noise. Define who acts, how quickly, and under what conditions.
- Run phishing simulations. Then deliver targeted training. Measure click-rate reduction over time.
- Review third-party access. Vendors, contractors, integrations — if the access is not actively needed, revoke it.
- Update your IR playbook. Make it usable at 3 AM. Role cards, contact trees, decision trees. Not a PDF nobody reads.
Cybersecurity is not a product, it is a practice. And like any practice, discipline matters more than inspiration.
Where this leaves us
Each of these stories carries the same underlying message: the attack surface keeps growing, and the defenders are still adjusting.
The organisations that survive the next wave will be the ones that treat visibility as a discipline, not a product.
There is no silver bullet. But there is absolutely a difference between trying and hoping. Choose the former.
Stay sharp. Stay questioning. And I will see you at the next brief.