KEV digest · 24–26 Oct 2026

Exploited now: 2 vulnerabilities added to CISA KEV, 24–26 Oct 2026

Mihai Marangoci, Gociux · 27 Oct 2026 · generated from CISA KEV + FIRST EPSS · 3 min read

In the window 24–26 Oct 2026, CISA added 2 vulnerabilities to the Known Exploited Vulnerabilities (KEV) catalog — each one has reliable evidence of exploitation in the wild. PHP Group accounts for 2 of the 2. US federal agencies must remediate them by 29 Oct 2026; treat that as the ceiling, not the target.

The 2 entries

CISA required action (every entry): Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Context

The catalog now holds 1,758 entries. 32 were added in the last 30 days, down from 41 in the 30 days before. Year to date, 274 additions in 2026 against 210 by the same date in 2025. For scale: 973 new CVEs were published in the same window. 2 confirmed-exploited additions is about 1 in 486 — which is why patching by severity alone does not scale.

Check your own stack

Run your own vendors and products through stack check — it is pre-filled with this digest's vendors and also gives you an RSS feed for future additions. The long-run picture is on CVE Trends.

How this is made: generated automatically every few days from the CISA KEV catalog and FIRST EPSS scores (probability of exploitation in the next 30 days, as of publication). Descriptions and required actions are CISA's own wording. Federal due dates apply to US agencies under BOD 22-01; for everyone else they are a sensible upper bound.