Summary
CVE-2026-86102 is a critical OS command injection vulnerability in the internal management API service of WatchGuard AP wireless access points. An attacker with network access to the device can send crafted requests to the internal API and execute arbitrary shell commands on the underlying operating system, without needing valid credentials. The issue carries a CVSS v4.0 base score of 9.3 (Critical), reflecting its network-exploitable, low-complexity path to full device compromise.
Technical details
- Root cause: The WatchGuard AP internal API service fails to properly neutralize special elements in user-supplied input before passing it to a system/shell command (CWE-78), combined with incorrect authorization checks on the internal API (CWE-863).
- Trigger conditions: An attacker only needs network reachability to the AP’s internal API service; no user interaction and no privileges are required to trigger the flaw.
- Attack vector: Network (AV:N) — exploitable remotely over the network path to the affected service, with low attack complexity and no privileges or user interaction required.
- Impact: Successful exploitation allows arbitrary OS command execution on the access point, giving an attacker full control over confidentiality, integrity, and availability of the device — potentially enabling persistence, traffic interception, or use of the AP as a pivot point into the broader network.
Affected software
- WatchGuard AP — versions 1.0 through 3.4.7 (inclusive)
Severity
- CVSS v4.0 Base Score: 9.3 (Critical)
- Vector:
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Mitigation and recommended actions
- Immediate: Upgrade all WatchGuard AP devices to version 3.4.8 or later, which contains the fix for this vulnerability.
- If immediate patching is not possible: Restrict network access to the AP’s internal management API to trusted management networks only, and ensure access points are not exposed to untrusted or public networks until patched.
- WatchGuard states there is no known active exploitation of this vulnerability in the wild as of publication, but given the low complexity and critical impact, patching should be prioritized.

