Why "critical" doesn't always mean "fix first"

Vulnerability management · November 2026 · About a 6 minute read

Run a vulnerability scanner over a typical small business and you'll get a long list, often with dozens of items marked "critical" or "high". No small team can fix them all at once. The question that matters is which ones to fix first, and the severity label alone doesn't answer it.

What the severity score actually measures

Most scanners rank findings with CVSS, the Common Vulnerability Scoring System. A CVSS score describes how bad things could be if someone exploited a flaw: could they take over the system, steal data, or just cause a nuisance? It's useful, but it says nothing about whether anyone is actually exploiting the flaw, or is likely to.

In practice, only a small share of published vulnerabilities are ever used in real attacks. Treating every "critical" as an emergency means a lot of effort goes into flaws nobody is using, while a "medium" that criminals are actively exploiting waits its turn.

Two free sources of real-world evidence

CISA's Known Exploited Vulnerabilities catalogue

The US Cybersecurity and Infrastructure Security Agency keeps a public catalogue of vulnerabilities with reliable evidence of exploitation in the wild, known as the KEV catalogue. If a flaw in something you run is on the list, attackers are using it now. These go straight to the top.

EPSS: the Exploit Prediction Scoring System

EPSS, maintained by FIRST, estimates the probability that a vulnerability will be exploited in the next 30 days, based on real-world data. It's updated daily and covers far more vulnerabilities than KEV. A high EPSS score is a strong hint that a flaw deserves attention soon, even before it appears on KEV.

Speed matters more than ever

Attackers are moving faster. VulnCheck found that in the first half of 2026, almost a quarter of known exploited vulnerabilities were attacked on or before the day they were made public, and the median time from publication to confirmed exploitation fell to 80 days. Verizon's 2026 report found exploited vulnerabilities had become the most common way attackers got in. A quarterly patching routine that treats everything equally can't keep up.

A simple way to prioritise

  • Fix today: anything internet-facing that's on the KEV catalogue
  • Fix this week: internet-facing flaws with a high EPSS score, and KEV items on internal systems
  • Schedule: everything else, in your normal update cycle, starting with the highest severity

Then adjust for your situation. A flaw on a server that isn't reachable from the internet is less urgent than the same flaw on your VPN gateway. A system holding customer data matters more than a test machine.

The bigger point

Small businesses don't fail at security because they don't care. They fail because they're handed long lists with no sense of order, and they run out of time. Prioritising by real-world evidence turns an impossible list into a short, achievable one.

This is how we rank every finding. Our Rapid Exposure Audit checks what you expose and sorts it into Fix today, This week and Schedule. Exposure Watch then alerts you each month when something new you run lands on the KEV catalogue.

Sources

  1. CISA, Known Exploited Vulnerabilities Catalog
  2. FIRST, Exploit Prediction Scoring System (EPSS)
  3. FIRST, Common Vulnerability Scoring System (CVSS)
  4. VulnCheck, State of Exploitation 1H 2026
  5. Verizon, 2026 Data Breach Investigations Report news release