Security Resilience

Patch Tuesday vs. the noise Monthly

Whose vulnerability count moved this month, and why it usually does not mean what it looks like. Updated 2026-07-25.

A vendor's monthly vulnerability count is mostly a publishing schedule, not a risk signal. This view separates the three things people confuse: a scheduled bulk disclosure, a steady release cadence, and a vendor whose flaws are actually being exploited. Read the last two columns, not the first.

VendorLast 30dPrior 30d ChangeYearKnown-exploited (yr)Read
Oracle1,1082684.1x1,6345bulk drop
Microsoft8537861.1x3,79236steady
Google5168600.6x2,45712steady
Linux Kernel3951,2160.3x5,3588steady
Apple2585800.4x2,23614steady
Apache132951.4x5551steady
Adobe1051320.8x8024steady
Mozilla72501.4x4260steady
Red Hat47710.7x2653steady
Openclaw42670.6x5740steady
IBM40730.5x5150steady
Dell39221.8x2831steady

Source: our vendor vulnerability stats, refreshed daily. "Known-exploited" counts entries on the CISA Known Exploited Vulnerabilities catalog over the trailing year. A change of 2.5x or more usually marks a scheduled bulk disclosure (for example a quarterly update), not a new problem.

A month over month jump is almost always a calendar, not a fire. When you triage, ignore the raw count and work the known-exploited column against software you actually run.