Widely deployed Cisco CW9800 Wireless Controller; unauthenticated DoS via malformed CAPWAP packets could disrupt wireless services.
CVE-2026-20086
Unauthenticated CAPWAP handling leads to DoS on Cisco CW9800 Wireless Controller.
Is CVE-2026-20086 being exploited?
Not confirmed. CVE-2026-20086 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-20086?
CVE-2026-20086 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-20086?
Not known from our data. No patch reference has been recorded for CVE-2026-20086, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-20086 affect?
CVE-2026-20086 affects Cisco Catalyst CW9800 Wireless Controller, Cisco IOS XE Wireless Controller Software. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-20086?
Monitor Cisco advisories; upgrade to fixed firmware when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can trigger device reload by sending malformed CAPWAP packets, causing DoS.
Patch when possible
- affected17.14.1
- affected17.15.1
- affected17.15.2
- affected17.15.3
- affected17.15.2b
- affected17.15.4
- affected17.15.4d
- affected17.16.1
- affected17.17.1
- affected17.18.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.