UK’s trusted IT infrastructure partner since 2003
Servnet
FinanceToolsConfiguratorGet in Touch
Topic · running coverage

Exploited vulnerabilities and patch alerts: latest coverage

Every actively exploited flaw and urgent patch we have covered, in one place, with the data on how fast flaws are now exploited and a short dated summary of where things stand. It also lists the updates that broke things, because rolling one back removes its security fixes too. This page adds no new reporting. Each line links to the full piece.

974
CVEs in Microsoft’s September 2026 security release, a record
−7 days
mean time to exploit in Mandiant’s 2026 reporting: abuse can start before disclosure
1,486
Microsoft security fixes a Windows 10 22H2 PC without Extended Security Updates had missed by 20 September 2026
68
Servnet pieces gathered here: 58 news, 3 insights, 2 explainers, 5 research

Newest piece 28 Oct 2026 · summary checked 28 Oct 2026 · coverage since 9 Sept 2025

Where it stands

Where things stand, as of 28 Oct 2026

A short summary of what our coverage shows. Every point links to the piece it comes from, which has the full detail and its sources.
  • The volume is the first problem. Microsoft’s September 2026 release listed a record 974 CVEs, after 622 in July; our Microsoft vulnerability statistics put that in context. Patching everything at once is no longer realistic, so triage by exploitation status first.
  • Exploitation often starts before disclosure. Mandiant puts the mean time to exploit at minus seven days, and VulnCheck found that 28.96% of 2025’s known-exploited vulnerabilities were exploited on or before the day their CVE was published. Our exploitation speed index has the detail.
  • Internet-facing appliances are still the front door. Since mid-September we have covered actively exploited flaws in Citrix NetScaler (two, confirmed by the NCSC), Ivanti Connect Secure (exploited since at least 1 October), Palo Alto PAN-OS and Cisco Secure Email Gateway.
  • PHP2Shell is the latest major case. Our census of 92 PHP release lines found 50 had a fix on release day and 13 still had none a week later. A working exploit exists and CISA lists both flaws as known-exploited, but no widespread compromise had been publicly evidenced by 27 October.
  • Patches can break things. September’s Windows Server updates broke Remote Desktop Services for some admins on Server 2019, 2022 and 2025, and rolling them back to restore service also removed fixes for two actively exploited zero-days. A September update could also break Active Directory sign-in for some Credential Guard machine accounts.
  • Unsupported systems fall further behind every month. A Windows 10 22H2 PC without Extended Security Updates had missed 1,486 Microsoft security fixes between support ending in October 2025 and 20 September 2026, 12 of them for flaws CISA lists as actively exploited.

Still unclear

  • Whether PHP2Shell will be exploited at scale. As of 27 October, working exploits had been built in the lab, real code execution had been caught on a honeypot deliberately made favourable to the flaw, attempts were widespread and CISA had listed both flaws as known-exploited, but no widespread compromise had been publicly evidenced.
  • How long a compromise can predate the patch. Google researchers traced Citrix NetScaler exploitation back to at least early September, before the 27–28 September disclosure, so patching does not prove a device was never breached.
  • Whether a device is clean after an Ivanti compromise. CISA warns that Ivanti’s own Integrity Checker Tool may miss attacks that run in memory.
Where to start

Read these first

Four pieces that between them cover the basics, the decisions and the data. The full list is further down.
01 LearnCVSS score explained: CVE, CVSS 4.0 and KEVWhat the identifiers and scores in every alert mean.02 LearnWhat is patch management, and why it mattersThe process behind keeping up.03 ResearchCVE exploitation speed index 2026Why monthly patch cycles no longer fit.04 ResearchPHP2Shell: what the flaws are, and who shipped a fixThe latest major case, end to end.
How our coverage of exploited vulnerabilities and patch alerts divides up
How Exploited vulnerabilities and patch alerts coverage divides across Servnet’s sectionsNews: 58; Insights: 3; Learn: 2, start with CVE, CVSS and KEV; Research: 5, start with How fast flaws are hitThis topic page68 pieces linkedNews58 piecesWhat happened, as it brokeNEWEST FIRSTSee the timeline belowInsights3 piecesDecisions and buyer guidesNEWEST FIRSTSee the timeline belowLearn2 piecesPlain-English basicsSTART WITHCVE, CVSS and KEVResearch5 piecesThe data, with sourcesSTART WITHHow fast flaws are hit

Scroll the chart sideways to see all of it →

Counts are every published piece linked from this page. Each section does a different job, so read across them rather than down one.

All coverage

Everything we have published on exploited vulnerabilities and patch alerts

Newest first. New news on this topic is added here automatically when it is published; the summary above is reviewed by hand and carries its own date.
Pieces published per month, by section
News 58Insights 3Learn 2Research 5
Exploited vulnerabilities and patch alerts: Servnet pieces published per month68 pieces across 14 months, stacked by section. 2025-09: 1; 2025-10: 0; 2025-11: 0; 2025-12: 0; 2026-01: 0; 2026-02: 0; 2026-03: 1; 2026-04: 0; 2026-05: 0; 2026-06: 0; 2026-07: 18; 2026-08: 13; 2026-09: 21; 2026-10: 14.0510152025Sep 2025: 1 piece (1 Learn)1Sep2025Oct 2025: 0 piecesOctNov 2025: 0 piecesNovDec 2025: 0 piecesDecJan 2026: 0 piecesJan2026Feb 2026: 0 piecesFebMar 2026: 1 piece (1 Insights)1MarApr 2026: 0 piecesAprMay 2026: 0 piecesMayJun 2026: 0 piecesJunJul 2026: 18 pieces (17 News, 1 Research)18JulAug 2026: 13 pieces (11 News, 1 Insights, 1 Research)13AugSep 2026: 21 pieces (17 News, 1 Insights, 1 Learn, 2 Research)21SepOct 2026: 14 pieces (13 News, 1 Research)14Oct

Scroll the chart sideways to see all of it →

Hover or tap a month for its breakdown. Every piece counted is listed below.

Whose products the flaws were in
Whose products the flaws were inMicrosoft: 8; SonicWall: 4; Cisco: 3; GitLab: 3; JFrog: 3; Linux and KVM: 3; VMware: 3; Adobe Commerce: 2; Apple: 2; Check Point: 2; Citrix: 2; Palo Alto Networks: 2; PHP: 2. One story each: 7-Zip, AI agent frameworks, Arista, BeyondTrust, Collabora, Drupal, Fastjson, Fortinet, Ivanti, Langflow, Other, PTC, Redis, Server BMCs, Several OS vendors, UEFI firmware.Microsoft: 8 storiesMicrosoft8SonicWall: 4 storiesSonicWall4Cisco: 3 storiesCisco3GitLab: 3 storiesGitLab3JFrog: 3 storiesJFrog3Linux and KVM: 3 storiesLinux and KVM3VMware: 3 storiesVMware3Adobe Commerce: 2 storiesAdobe Commerce2Apple: 2 storiesApple2Check Point: 2 storiesCheck Point2Citrix: 2 storiesCitrix2Palo Alto Networks: 2 storiesPalo Alto Networks2PHP: 2 storiesPHP2

One story each (16): 7-Zip, AI agent frameworks, Arista, BeyondTrust, Collabora, Drupal, Fastjson, Fortinet, Ivanti, Langflow, Other, PTC, Redis, Server BMCs, Several OS vendors, UEFI firmware.

Scroll the chart sideways to see all of it →

News stories on exploited or critical flaws, by vendor. Updates that broke things are counted separately below.

October 2026 14

September 2026 19

August 2026 13

July 2026 17

When the update is the problem

Updates that broke something in production. Each forces a trade-off between keeping the security fixes and keeping the system working.

What to do

Acting on it

Where Servnet can help, and the free tools that put numbers on it for your own estate.
Vulnerability managementFind, rank and close exposure, starting with what is exploited.Open →Managed detection and responseFor when exploitation starts before the patch exists.Open →Server end-of-life checkerSee when your servers stop getting firmware and OS fixes.Open →Windows 10 end-of-life calculatorCost the Extended Security Updates against replacing devices.Open →
Questions

Common questions

What does “actively exploited” mean?

Attackers are using the flaw in real attacks, not just in a proof of concept. CISA’s Known Exploited Vulnerabilities (KEV) catalogue lists such flaws with fix deadlines for US federal agencies, and cyber insurers, auditors and NCSC-aligned frameworks routinely use it as a benchmark for what should have been patched first. Our explainer on CVE, CVSS and KEV covers how the three fit together.

How quickly should we patch?

Cyber Essentials expects critical and high-risk updates within 14 days. For internet-facing systems with a known-exploited flaw, that is too slow: exploitation now often begins before disclosure, and India’s CERT-In sets a 12-hour deadline, where feasible, for that class. Patch exploited, internet-facing flaws first, then work down.

Should we roll back an update that breaks something?

Only knowingly. Admins reported that rolling back September 2026’s Windows Server updates restored Remote Desktop Services, but it also removed fixes for two actively exploited zero-days. If you roll back, reduce exposure another way, for example by restricting access to the affected service, until a fixed update ships.

More topics

Other running coverage

Ransomware and cyber attacks in the UK42 pieces · newest 21 Oct 2026Cloud outages and IT resilience19 pieces · newest 23 Oct 2026All topicsWhat topic pages are, and how they differ from News, Insights, Learn and Research.

Topic pages summarise Servnet’s own published coverage for information only; they are not security, legal or financial advice. Facts and sources are in the linked pieces, which follow our editorial standards. Spotted something out of date? Tell us at webmaster@servnetuk.com.

Talk to a UK specialist

Get expert advice or a no-obligation quote — servers, storage, networking, maintenance, finance and cloud. We reply the same working day.

or call 0800 987 4111