WatchGuard AP Improper Access Control in API Service Allows Unauthenticated Access

Why this deserves its current priority

CVSS is 9.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps WatchGuard/WatchGuard AP (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for WatchGuard/WatchGuard AP.
2. 2Review the reported fix. Source-reported solution: WatchGuard AP 3.4.8

Evidence timeline and material changes

1. Published upstream

   Sep 28, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 28, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 28, 2026

Sources and claim methodology

• Source referencepsirt.watchguard.com

Related CVEs

• WatchGuard AP Command Injection in Internal Management API Allows Command ExecutionSame watchguard/watchguard ap package
• WatchGuard AP Authenticated Command Injection in Diagnostic CLISame watchguard/watchguard ap package
• PMWeb encryptionhelper.dll information disclosureAlso CWE-284
• agentverus agentverus-scanner context.js isSecurityDefenseSkill reliance on untrusted inputs in a security decisionSame generic ecosystem
• Tencent AI-Infra-Guard File Access dir_actions.py startsWith path traversalSame generic ecosystem
• D-Link DI-8400 Web Administration Service menu_nat_more.asp menu_nat_more_asp stack-based overflowSame generic ecosystem