Skip to content
Welcome, thoughtbot's Giant Robots listeners!Start here
Known Exploited Vulnerabilities
AI-generated illustration
ConceptUS

Known Exploited Vulnerabilities

CISA's catalogue of CVEs confirmed as actively exploited; mandatory patch deadlines for US federal agencies.

On 2 September, Known Exploited Vulnerabilities recorded 37 new entries, 24 with three-day federal remediation deadlines. The catalogue remains CISA's operational list of software flaws confirmed under active exploitation.

Last refreshed: 22 September 2026 · Appears in 1 active topic

Key Question

Is the 2022 patch or the 2024 patch the one breaking into networks right now?

Timeline for Known Exploited Vulnerabilities

#14 8 Oct

Received five 2015-2023 CVEs with 11 October deadlines

Cybersecurity: Threats and Defences: Ten agencies name Beijing firm in hacks
#14 30 Sept

Received 43 additions in September

Cybersecurity: Threats and Defences: CISA set three-day deadlines on 34 flaws
#14 30 Sept
#14 27 Sept

Mentioned in: Citrix replaces its own NetScaler fix

Cybersecurity: Threats and Defences
#14 22 Sept
View full timeline →

Background

Known Exploited Vulnerabilities is CISA's catalogue of Common Vulnerabilities and Exposures entries confirmed as actively exploited. Its addition of a flaw starts mandatory remediation deadlines for US Federal Civilian Executive Branch agencies, while private-sector defenders use it as a high-confidence public signal that patching has become urgent. On 10 June 2026, the catalogue had reached 1,627 entries.

The catalogue was established under Binding Operational Directive 22-01 in November 2021. That directive made deadlines part of federal vulnerability management, rather than leaving agencies to rank known flaws solely by severity scores. A 15 May 2026 listing involving Microsoft Exchange showed the practical consequence: agencies received a mandatory Deadline while no vendor patch was available.

On 10 June 2026, Binding Operational Directive 26-04 replaced the former fixed regime with four risk-based remediation windows. The catalogue's lasting importance is therefore twofold: it identifies exploitation that has crossed from theoretical risk into observed threat activity, and it translates that evidence into a federal timetable for action.

Key Issues
Patch deadlines

KEV deadlines stayed at three days

On 2 September 2026, CISA had added 37 vulnerabilities to Known Exploited Vulnerabilities since 3 August. Twenty-four, or 65 per cent, carried a three-day Deadline for federal agencies. That share had fallen from 87 per cent in the preceding period, but the typical deadline remained three days.

For the catalogue, the change shows that its urgency signal now varies within a batch rather than moving in one direction. On 10 June 2026, Binding Operational Directive 26-04 replaced the earlier fixed approach with risk-based windows of three, 14 or 60 days, or the next upgrade cycle. Known Exploited Vulnerabilities therefore remains both a record of active exploitation and the mechanism that starts federal remediation obligations.

Legacy exposure

KEV exposes old patch debt

On 14 April 2026, CISA added CVE-2009-0238, a 17-year-old Microsoft Office flaw, to Known Exploited Vulnerabilities after confirming active exploitation. The listing turned a legacy-software weakness into a current federal remediation matter.

On 14 July 2026, the catalogue reached 1,638 entries after CISA added seven flaws, including an 18-year-old Cisco router vulnerability with a fix available since 2008. For Known Exploited Vulnerabilities, such additions show why catalogue inclusion cannot be treated as a measure of software age or novelty. It records evidence that attackers are using a flaw now, including flaws organisations may have long assumed were settled.

Common Questions

KEV deadlines stayed at three days

Does the CISA KEV catalogue apply to private companies?
BOD 26-04 and its predecessor BOD 22-01 impose mandatory remediation deadlines only on US Federal Civilian Executive Branch agencies. Private-sector organisations are not legally bound but widely treat KEV addition as the strongest available signal of active exploitation.Source: event
How many CVEs are in the CISA Known Exploited Vulnerabilities catalogue?
As of catalogue version 2026.07.29 the KEV catalogue held 1,656 entries, with nothing added between 30 July and 3 August 2026. The growth rate has slowed from the roughly two-a-day pace tracked through June to nearer 0.78 CVEs a day since BOD 26-04's risk-tiered triage took effect on 10 June 2026.Source: event
What replaced BOD 22-01 for CISA KEV patch deadlines?
CISA replaced BOD 22-01 with BOD 26-04 on 10 June 2026. The new directive uses a four-tier risk model (3 days, 14 days, 60 days, or next upgrade cycle) based on exploitability, exposure, asset criticality, and threat actor behaviour.Source: event
What happens when CISA sets a KEV patch deadline before a vendor has shipped a fix?
In May 2026, CISA did this three times in twelve days: PAN-OS CVE-2026-0300 (Deadline 9 May, Palo Alto patches from 13 May), Cisco SD-WAN CVE-2026-20182 (Deadline 17 May), and Exchange CVE-2026-42897 (Deadline 29 May, Microsoft patch not yet shipped). Agencies must implement available mitigations and accept a documented non-compliance posture until the vendor patch ships.Source: CISA KEV / ED 26-03
What was the shortest KEV remediation deadline in 2026?
Three Cisco Catalyst SD-WAN Manager CVEs added to KEV on 20 April 2026 carried a 3-day federal remediation Deadline, the shortest in the April cycle. In May 2026, Cisco SD-WAN CVE-2026-20182 (CVSS 10.0) also carried a 3-day Emergency Directive Deadline from CISA.Source: CISA KEV / April and May 2026
What was the shortest KEV remediation deadline in April 2026?
Three Cisco Catalyst SD-WAN Manager CVEs added to KEV on 20 April 2026 carried a 3-day federal remediation Deadline — the shortest window in the April 2026 additions, signalling CISA's assessment of high active-exploitation risk.Source: CISA KEV / April 2026

KEV exposes old patch debt

Why did CISA take a month to add the Fortinet FortiSandbox flaw to KEV?
CrowdSec detected in-the-wild exploitation of FortiSandbox CVE-2026-39808 on 17 June 2026, but CISA did not ADD it to the Known Exploited Vulnerabilities catalogue until 16 July, a one-month gap that raises questions about detection-to-listing speed under the new risk-tiered BOD 26-04 model.Source: CrowdSec
Has the pace of new CISA KEV additions slowed down?
Yes. The 5-14 July 2026 window added only seven CVEs, the quietest fortnight tracked, against a roughly two-a-day pace through June, a possible early sign BOD 26-04's risk-tiered triage is changing what gets listed.Source: event
What is the oldest vulnerability in CISA's KEV catalogue?
CVE-2008-4128, an 18-year-old Cisco IOS CSRF flaw, added in the 5-14 July 2026 window, the oldest entry the catalogue has carried since the beat began tracking it.Source: event
What is CISA's Known Exploited Vulnerabilities catalogue?
CISA's KEV catalogue lists CVEs with confirmed active exploitation. Federal agencies must patch KEV CVEs within set deadlines under Binding Operational Directive 22-01. It is the primary public signal of active exploitation used by private-sector patch-prioritisation Teams worldwide.Source: CISA
Will CISA budget cuts affect the KEV catalogue?
The Trump administration's FY27 budget proposes cutting CISA by $707m, affecting 860 staff. The KEV catalogue's signal quality and frequency depend on CISA's analyst capacity to monitor exploitation and write advisories. A materially reduced CISA would slow catalogue additions and reduce the advisory detail that private-sector patch Teams rely on.Source: CISA budget proposal FY27
Are the vulnerabilities in CISA's KEV catalogue mostly new or old?
A significant share are years old. The June 2026 batch included CVE-2022-0492 (Linux cgroups, four years old) and CVE-2024-21182 (Oracle WebLogic, patched January 2024). A 17-year-old Microsoft Office bug was added in the April 2026 window. KEV is a forcing function across legacy estates, not a zero-day service.Source: CISA KEV
Source Material