Cyber trends 2026

Exploits Overtook Stolen Passwords in 2026: Why Patching Is Now Urgent

For the first time in the 19 year history of Verizon's breach report, exploiting software flaws beat stolen credentials as the top way into organisations. Here is why that happened and what good patching looks like.

patchingvulnerabilitiesDBIRKEV

Updated November 2026

The headline finding

Verizon released its 2026 Data Breach Investigations Report on 19 May 2026. Its news release states that nearly a third (31%) of breaches started with vulnerability exploitation, surpassing stolen credentials as the biggest point of entry for the first time in 19 years of the report. CyberScoop's coverage adds that exploited vulnerabilities rose from 20% of known initial access vectors the year before.

Verizon also said AI is being used by attackers to speed up exploitation of known vulnerabilities, shrinking the defence window from months to hours. Note that the report uses 2025 data.

Patching is getting slower

CyberScoop reported these figures from the DBIR:

  • Only 26% of critical vulnerabilities in the CISA Known Exploited Vulnerabilities (KEV) catalog were fully remediated by the organisations Verizon studied in 2025, down from 38% the year before.
  • The median time to fully patch rose to 43 days, from 32 days.
  • The median number of KEV vulnerabilities organisations had to patch rose from 11 to 16.

In short, there are more urgent bugs and teams are struggling to keep up. The report described vulnerability management as a "sisyphean" task.

What is the KEV catalog?

CISA, the US cybersecurity agency, maintains the Known Exploited Vulnerabilities catalog: a public list of vulnerabilities with evidence of real world exploitation. It is free, and security teams worldwide use it to prioritise. If a bug is on KEV and you run that software, it should go to the top of your list.

In India, CERT-In publishes advisories and vulnerability notes for products used here, such as monthly Microsoft and SAP updates. Subscribing to or regularly checking these is a good habit for any IT team.

Why organisations patch slowly

  • Too many vulnerabilities and too few people.
  • Fear of breaking things, especially on old or critical systems.
  • Unknown assets: you cannot patch a server nobody remembers exists.
  • Vendor delays or end of life products with no patches at all.
  • Downtime windows that are hard to schedule.

A practical patching plan

  1. Know what you have. Keep an asset inventory, including cloud services and internet facing devices.
  2. Prioritise by real risk: internet facing first, then known exploited (KEV or CERT-In advisories), then critical severity, then the rest.
  3. Set target times. For example, emergency patches for exploited internet facing bugs within days, routine patches monthly.
  4. Test quickly, on a small group first, then roll out.
  5. Have a fallback: if you cannot patch, apply the vendor's mitigation, restrict access or take the system offline.
  6. Replace end of life systems that no longer get updates.
  7. Verify with a scan after patching.

For your own devices

The same lesson applies at home. Turn on automatic updates for your phone, laptop, browser and apps. Restart when asked. Replace old phones that no longer receive security updates if you use them for banking. CERT-In's April 2026 advisory on AI driven risks specifically tells individuals to enable automatic updates and patch quickly, because AI driven exploits can spread fast.

For students and freshers

Vulnerability management is a solid career skill. Learn to read a CVE entry, understand CVSS scores and their limits, check KEV, and practise scanning your own lab with free tools. Being the person who can say "these five things must be patched this week, and here is why" makes you valuable in any IT team.

Frequently asked questions

Why not just patch everything immediately? Large organisations run thousands of systems, and some patches can break business critical software. That is why prioritisation and quick testing matter more than trying to patch everything at once.

What does "end of life" mean? The vendor no longer releases security updates. Any new vulnerability will stay unfixed forever, so plan to replace such software or devices.

Are automatic updates safe to leave on at home? For personal devices, yes. The risk of an unpatched device is much higher than the small chance of an update causing problems.

What is a zero day? A vulnerability that attackers exploit before a patch is available. You cannot patch it yet, so defences like least privilege, segmentation and monitoring help limit the damage.

Educational content, not legal advice. Check official sources before you rely on it. If you have lost money, call 1930 now. Terms