WatchGuard AP 3.4.8 Fixes Three Access and Command-Injection Vulnerabilities
Tech GuruQuick Answer
WatchGuard published CVE-2026-101891, CVE-2026-86102, and CVE-2026-87969 for WatchGuard AP releases from 1.0 through releases before 3.4.8. Two issues permit unauthenticated network access to an API session or operating-system command execution; the third permits command execution by an authenticated administrator. Upgrade affected access points to WatchGuard AP 3.4.8.
Confirm Scope And Apply The Supported Fix
What to do now: Inventory WatchGuard AP releases before 3.4.8, restrict management and internal API reachability while updating, deploy WatchGuard AP 3.4.8 through the supported channel, validate AP management and client connectivity, and retain version and change evidence.
Last verified: 2026-09-29 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | WatchGuard AP releases from 1.0 through releases before 3.4.8 |
|---|---|
| Advisory | CVE-2026-101891 / CVE-2026-86102 / CVE-2026-87969 |
| CVEs | CVE-2026-101891, CVE-2026-86102, CVE-2026-87969 |
| Authoritative release date | 2026-09-28 16:51:27 UTC (WatchGuard PSIRT RSS publication time) |
| Authority revision date | 2026-09-28 (no later material revision stated by WatchGuard when verified) |
| Affected versions | WatchGuard AP releases from 1.0 through releases before 3.4.8. |
| Fixed version | WatchGuard AP 3.4.8 |
| CVSS base score | 8.6 / 9.3 (CVSS v4.0) |
| CVSS severity | High to Critical |
| Exploitation status | WatchGuard is not aware of exploitation of these vulnerabilities in the wild; no exploitation claim is inferred. |
What Changed
WatchGuard disclosed an unauthenticated API-session issue, an internal management API command-injection issue, and an authenticated diagnostic CLI command-injection issue. The two network-access issues are rated 9.3 Critical and the authenticated CLI issue is rated 8.6 High under CVSS v4.0.
What To Validate Now
- Inventory. Locate WatchGuard access points, record installed release, management-plane and internal API reachability, administrative access paths, site owner, and dependent wireless services.
- Establish applicability. Compare each access point with the authority's affected range of WatchGuard AP 1.0 through releases before 3.4.8. Do not infer applicability from product family or severity alone.
- Remediate. Upgrade affected access points to WatchGuard AP 3.4.8 through WatchGuard's supported update channel. Until completion, restrict management and internal API access to approved administration networks.
- Validate. Confirm release 3.4.8 or later on every in-scope AP, exercise administrative and diagnostic workflows, validate client association and connectivity, review relevant management logs, and document exceptions.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Coordinate wireless changes to preserve site coverage and management reachability. WatchGuard says it is not aware of exploitation in the wild; that statement does not prove a particular environment is uncompromised.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
