Our Cyber Insights Four vulnerabilities are already being exploited. So why are we still patching by score?

Insights

I grew up in the UK, where you learned fairly quickly that if somebody was already trying the door handle, that particular door deserved your attention before you started worrying about whether the upstairs window might need a better lock.

Cybersecurity occasionally needs the same bit of common sense.

On the 18th November 2026, CISA added four vulnerabilities to its Known Exploited Vulnerabilities, or KEV, catalogue because there is evidence that attackers are already exploiting them.

They affect:

  • Synology DiskStation Manager (DSM): CVE-2024-10441
  • BerriAI LiteLLM: CVE-2026-40217
  • Apache Axis: CVE-2026-90436
  • Vanderbilt University REDCap: CVE-2026-90817 [cisa.gov]

Four very different technologies.

One very important thing in common.

Attackers have got there first.

The problem with the traditional patching queue

For years, vulnerability management has commonly revolved around severity. You know the sequence, find the vulnerabilities, look at the CVSS scores, put the critical ones at the top, then give the patching teams a number of days to patch them. Finally measure whether they met the SLA.

Neat. Measurable. Easy to put on a dashboard.

But attackers haven’t agreed to follow our spreadsheet.

A vulnerability with a frightening theoretical severity but no practical route into your environment may present less immediate danger than another vulnerability with a slightly lower score that is sitting on an internet-facing system and being actively exploited today.

That difference matters. In fact, CISA’s own direction is increasingly explicit. Its BOD 26-04 approach requires US federal civilian agencies to prioritise rapid remediation of high-risk KEV vulnerabilities on publicly exposed assets where successful exploitation can provide total control, while lower-risk vulnerabilities can be deferred. The directive applies to US federal agencies, but the principle travels rather well.

Patch according to the real risk, not simply numerical severity.

Look at what these four vulnerabilities touch

The latest additions are interesting because they are not four versions of the same problem.

We have network-attached storage, an LLM gateway, a legacy web-services framework, and a research data platform.

That should get the attention of quite a few technology leaders.

Particularly noteworthy is LiteLLM.

Organisations are rapidly introducing AI infrastructure, gateways and supporting platforms into their environments that already contain years of conventional technology. Security teams therefore have another technology layer to discover, patch, monitor and govern.

At the other end of the spectrum sits Apache Axis, technology that may survive quietly inside older applications long after everybody has stopped talking about it.

That combination is uncomfortable.

Your attack surface isn’t merely the shiny new technology being installed this year.

It is the shiny new technology plus everything you forgot you were still running.

Patch priority needs another question

When a new vulnerability appears, “How severe is it?” remains a perfectly sensible question.

It just shouldn’t be the only one.

I would want the vulnerability team asking:

  • Is it being actively exploited?
  • Do we actually run the affected product and version?
  • Is it internet-facing or otherwise reachable by an attacker?
  • What privilege or control does successful exploitation provide?
  • What business service sits behind it?
  • Is there evidence somebody has already attempted exploitation in our environment?

That will produce a very different patch queue, and importantly, once exploitation is known, the job may no longer be simply patch and close the ticket.

You may need to investigate whether the system was compromised before you patched it.

CISA’s latest vulnerability-management direction specifically introduces expectations around checking for previous compromise in these circumstances.

That is an important distinction.

Installing the patch closes the door.

It doesn’t tell you whether somebody walked through it yesterday.

Change the dashboard

This is where I would challenge security leaders.

If your vulnerability dashboard tells the board you have 62 critical vulnerabilities and 184 high vulnerabilities, what exactly should they conclude?

  • Is the organisation in trouble?
  • Are those vulnerabilities exploitable?
  • Are they exposed?
  • Is anyone exploiting them?

Nobody can tell from the numbers alone.

I would rather see something like:

Known exploited + externally exposed + critical business service = act now

Known exploited + internally exposed = accelerated remediation

High theoretical severity + no exposure + compensating controls = scheduled remediation

That isn’t ignoring vulnerability severity, it is putting severity into context.

Patch what the attacker cares about

There will always be more vulnerabilities than security teams would like.

Trying to treat every single one with equal urgency creates the opposite of urgency. Everything becomes critical, teams become buried in patching activity, exceptions accumulate and the genuinely dangerous vulnerabilities become another row in the queue.

The four vulnerabilities added by CISA this week provide a useful reminder.

It is not because they have CVE numbers it because somebody is using them.

That is threat intelligence you can act upon.

Vulnerability management should therefore be driven by a combination of attacker activity, exposure, exploitability, asset importance and severity.

Because when somebody is already trying the door handle, I would suggest fixing that door first.

The Summary

Attackers do not prioritise vulnerabilities according to your patching spreadsheet.

If a vulnerability is already being exploited, fix that door first and then check whether somebody has already walked through it.

About Northwick Cybersecurity

Northwick Cyber is the cyber security services brand of Bushey Pty Ltd, an Australian-based specialist consultancy with reach across the Asia-Pacific. We help organisations find their cyber security weaknesses before attackers do, see threats as they happen, and recover quickly when something goes wrong.

How we help

  • Penetration testing. We test your websites, applications, networks and cloud environments the way a real attacker would, then give you clear, prioritised fixes. After an event like PHP2Shell, a targeted test confirms whether your exposure is actually closed.
  • 24×7 monitoring. We watch your systems around the clock for signs of intrusion, so suspicious activity is caught and acted on early, not found weeks later.
  • Incident response. If you suspect a breach, we contain it, work out what happened and get you back to normal operations, with clear reporting for executives, Boards, insurers and regulators.

Why it matters for Boards

Cyber risk is now a governance responsibility. Northwick Cyber gives leaders an independent view of where they’re exposed and evidence that issues have been fixed, plus a trusted partner on call when it counts. We draw on Bushey’s long experience delivering complex technology programmes for corporate and government clients.

#CyberSecurity #VulnerabilityManagement #ThreatIntelligence #CyberRisk #NorthwickCybersecurity

Scroll
Drag

About Us

Northwick Cybersecurity is a dedicated brand from Bushey Pty Ltd. that is focused on supporting your Cybersecurity needs and partnering to keep your business data and systems safe from data theft and breaches.

Contact Info