2026 passes 100,000 CVEs, so here is how to prioritise patching

Started by Shannon44, Today at 07:47 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Topic: 2026 passes 100,000 CVEs, so here is how to prioritise patching   Views(Read 80 times)
Active members in this topic:
Shannon44(1)

Shannon44

This year's count of published vulnerabilities has passed a remarkable milestone. The Register reports that VulnCheck counted 100,222 CVEs at about 4pm UTC on 13 November, more than double the total for 2025

Microsoft fixed 1,094 flaws this Patch Tuesday, after 1,474 the month before. Only about 1.4 percent, or 1,363, are on VulnCheck's known exploited list

The median time to exploitation fell from 120 days in 2025 to 80 days in the first half of 2026. CrowdStrike says 88 percent of exploitation using public proof of concept code happened within 48 hours of release

VulnCheck's Josh Bressers said AI driven vulnerability hunting is behind most of the increase, and that the industry now has a data problem rather than a security problem. That explanation is his view, and the count is a snapshot

Nobody can patch 100,000 flaws, so focusing on the small share that are actively exploited is the practical approach. Known exploited lists are a great starting point for any team. Patching internet facing systems first remains the best rule of thumb

How does your team decide which vulnerabilities to patch first? And are AI tools helping or hurting security overall?

Making the forum slightly smarter one post at a time