Quick answers
- Is CVE-2026-111107 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111107 being exploited in the wild.
- How severe is CVE-2026-111107?
- Informational severity, published 27 October 2026.
- Which products and versions are affected?
- Watchguard Fireware OS 2025.1 to 2026.3, 12.0 to 12.12.3; Watchguard Fireware OS T15/T35 12.0 to 12.5.21.
- Is there a fix for CVE-2026-111107?
- Yes: fixed in Fireware OS 2026.4, Fireware OS 12.12.4, Fireware OS 12.5.22. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111107 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-111107?
- Check whether you run Watchguard Fireware OS or Watchguard Fireware OS T15/T35 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Fireware OS 2026.4, Fireware OS 12.12.4, Fireware OS 12.5.22
Technical details
A NULL pointer dereference in the Fireware OS management interface can be triggered by a specially crafted unauthenticated login request from the network. Repeated exploitation causes denial of service by terminating the management service and active administrator sessions. The vulnerability stems from improper input validation and uncaught exception handling (CWE-476, CWE-248).
Affected products
- WatchGuard Fireware OS 2025.1 to 2026.3, 12.0 to 12.12.3
- WatchGuard Fireware OS T15/T35 12.0 to 12.5.21
Timeline
- 2026-10-27: disclosed