KEV digest · 2–4 Nov 2026
In the window 2–4 Nov 2026, CISA added 2 vulnerabilities to the Known Exploited Vulnerabilities (KEV) catalog — each one has reliable evidence of exploitation in the wild. The additions span 2 different vendors. 1 entry carry CVE IDs two or more years old — the oldest, CVE-2024-27834, shows that legacy bugs keep getting exploited long after disclosure. US federal agencies must remediate them by 6 Nov 2026 – 18 Nov 2026; treat that as the ceiling, not the target.
Every addition this month in one list: CISA KEV November 2026 · all months: CISA KEV by month.
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.
WordPress · WordPress Core
WordPress WordPress Core contains a time-of-check time-of-use (TOCTOU) race condition vulnerability that could allow unauthenticated attackers to execute code on the server during the upgrade window. This is due to predictable, web-accessible staging paths used during full-package core upgrades.
added 2026-11-03 · federal due date 2026-11-06
Apple · Multiple Products
Apple iOS, iPadOS, macOS, Safari, tvOS and watchOS 10.5 contain an improper authentication vulnerability which could allow an attacker with arbitrary read and write capability to bypass pointer authentication.
added 2026-11-04 · federal due date 2026-11-18
The catalog now holds 1,768 entries. 34 were added in the last 30 days, down from 39 in the 30 days before. Year to date, 284 additions in 2026 against 216 by the same date in 2025. For scale: 1,614 new CVEs were published in the same window. 2 confirmed-exploited additions is about 1 in 807 — which is why patching by severity alone does not scale.
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.
We wire KEV and EPSS into your scanner, SIEM and ticketing, so only the exploited CVEs you actually run reach your team — with deadlines an auditor will accept.
Get in touch →