Post-EoL Security Exposure
Post-security-support SKUs matched to affected platforms in CISA's Known Exploited Vulnerabilities catalog.
Networking coverage audit
Platform mapping and support-date coverage are separate. These counts describe the current KEV snapshot, not installed-device exposure. Reviewed out-of-catalog entries concern other product lines; unmapped entries remain unresolved.
| Vendor | Vendor KEVs | Mapped | Unmapped | Reviewed outside catalog | Products with unknown support end |
|---|
KEV mapping coverage gaps
These KEV product groups have no correlation rule. They are not included in the matched-SKU counter; this is unknown coverage, not a finding of no exposure.
| Vendor | KEV product group | KEV entries |
|---|---|---|
| Progress | LoadMaster | 1 |
| Progress | Kemp LoadMaster | 1 |
| Progress | Telerik Report Server | 1 |
| Progress | WS_FTP Server | 1 |
| Progress | MOVEit Transfer | 1 |
| Progress | Telerik UI for ASP.NET AJAX | 1 |
| Progress | ASP.NET AJAX and Sitefinity | 1 |
This is not a CVE search tool. Every entry below is a specific device in our catalog that (1) is past the vendor's end-of-vulnerability-security-support or last-date-of-support date and (2) runs a platform listed in CISA's Known Exploited Vulnerabilities (KEV) catalog. The vendor is not patching these devices. The vulnerabilities are being exploited in the wild.
Correlation is at the platform level (Junos OS, PAN-OS, BIG-IP, SonicOS, Firebox, etc.). A specific CVE may affect only certain OS versions; the device may have received the patch before the vendor cut off support. Counts represent SKUs, including variants, rather than deployed devices or unique hardware models.
By vendor
Counts reflect post-EoL models running on an affected platform. A specific firmware version may not be vulnerable — verify with the vendor's PSIRT advisory.
| Vendor | Models on platform | Distinct CVEs | Ransomware-linked |
|---|---|---|---|
| Cisco | 2217 | 71 | 3 |
| Juniper | 1142 | 7 | 0 |
| Fortinet | 527 | 25 | 13 |
| QNAP | 217 | 10 | 9 |
| Arista | 210 | 1 | 0 |
| SonicWall | 105 | 18 | 12 |
| WatchGuard | 92 | 4 | 1 |
| Check Point | 81 | 3 | 2 |
| F5 Networks | 52 | 8 | 4 |
| Zyxel | 45 | 10 | 1 |
| Sophos | 39 | 3 | 0 |
| Zimbra | 37 | 19 | 6 |
| NETGEAR | 36 | 2 | 0 |
| Atlassian | 19 | 1 | 0 |
| Palo Alto | 19 | 13 | 6 |
| Progress | 19 | 2 | 1 |
| BeyondTrust | 18 | 1 | 0 |
| D-Link | 13 | 14 | 1 |
| VMware (Broadcom) | 8 | 16 | 7 |
| Sangoma | 7 | 3 | 0 |
| Citrix | 4 | 21 | 4 |
| Acronis | 1 | 1 | 0 |
| Veeam | 1 | 3 | 3 |
Flagged models
19 flagged devices (progress).
| Newest CVE added | Device | Vendor | CVEs | Ransom |
|---|---|---|---|---|
| WhatsUp Gold 16.0 | Progress | 2 | Yes | |
| WhatsUp Gold 16.1 | Progress | 2 | Yes | |
| WhatsUp Gold 16.2 | Progress | 2 | Yes | |
| WhatsUp Gold 16.3 | Progress | 2 | Yes | |
| WhatsUp Gold 16.4 | Progress | 2 | Yes | |
| WhatsUp Gold 16.5 | Progress | 2 | Yes | |
| WhatsUp Gold 17.0 | Progress | 2 | Yes | |
| WhatsUp Gold 17.1 | Progress | 2 | Yes | |
| WhatsUp Gold 18.0 | Progress | 2 | Yes | |
| WhatsUp Gold 19.0 | Progress | 2 | Yes | |
| WhatsUp Gold 19.1 | Progress | 2 | Yes | |
| WhatsUp Gold 19.2 | Progress | 2 | Yes | |
| WhatsUp Gold 20.0 | Progress | 2 | Yes | |
| WhatsUp Gold 21.0 | Progress | 2 | Yes | |
| WhatsUp Gold 21.1 | Progress | 2 | Yes | |
| WhatsUp Gold 22.0 | Progress | 2 | Yes | |
| WhatsUp Gold 22.1 | Progress | 2 | Yes | |
| WhatsUp Gold 23.0 | Progress | 2 | Yes | |
| WhatsUp Gold 23.1 | Progress | 2 | Yes |
Operators running any device in this list should treat it as a compensating-control scenario under NIST SA-22 and the equivalent PCI-DSS, HIPAA, and cyber-insurance guidance. See the Compliance and Insurance page for clause-level context and control options.
Source: CISA Known Exploited Vulnerabilities catalog. Snapshot refreshed weekly.