Exploitation timeline
Threadlinqs has recorded 7 WatchGuard CVEs published between and . The busiest month was 2026-09 (5 new CVEs). None of them is listed in CISA KEV yet.
Most exploited vulnerabilities
Ranked with CISA KEV listings first, then EPSS exploit probability, then CVSS score. Showing 7 of 7 tracked WatchGuard CVEs.
- CVE-2026-86134high 8.7EPSS 0.4%
- CVE-2026-86104high 8.7EPSS 0.4%
- CVE-2026-18145high 8.6EPSS 0.3%
- CVE-2026-86131critical 9.2EPSS 0.3%
- CVE-2026-57909critical 9.4EPSS 0.3%
- CVE-2026-101891critical 9.3EPSS 0.3%
- CVE-2026-57910critical 9.3EPSS 0.2%
Products affected
Threadlinqs normalises CPE and CNA product records across all 7 CVEs; 3 distinct WatchGuard products are affected. The most frequently affected:
- Fireware OS 4 CVEs
- Agent 2 CVEs
- AP 1 CVE
Threat activity
2 tracked threat campaigns reference WatchGuard products or exploit WatchGuard CVEs:
How to prioritise WatchGuard patching
This order follows the data Threadlinqs holds for WatchGuard, not a generic severity checklist:
- No WatchGuard CVE is in CISA KEV yet, so rank by exploit probability instead.
- Outside KEV, the highest EPSS scores are CVE-2026-86134 (0.4%), CVE-2026-86104 (0.4%), CVE-2026-18145 (0.3%).
- 4 CVEs score Critical and 3 High on CVSS v3 (maximum 9.4, average 9); sequence these after KEV and high-EPSS items.
About this data
Vendor attribution comes from the CNA and CPE product records of each CVE, folded to one vendor name; CVSS, EPSS and KEV status are read from the Threadlinqs CVE catalog; campaign and actor links come from tracked threat records. Counts reflect the data as of 2026-10-05 and refresh daily.