Quick answers
- Is CVE-2026-90441 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-90441 being exploited in the wild.
- How severe is CVE-2026-90441?
- Informational severity, published 30 September 2026.
- Which products and versions are affected?
- Watchguard Fireware OS Default: 2026.3 before 2026.3.2, 2025.0 before 2026.2.3, 12.0 before 12.12.3; T15/T35: 12.0 before 12.5.21.
- Is there a fix for CVE-2026-90441?
- A patch was published on 2026-09-29: Fireware OS 2026.3.2, 2026.2.3, 12.12.3, 12.5.21 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-90441 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-90441?
- Check whether you run Watchguard Fireware OS 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.
Technical details
A missing authorization vulnerability (CWE-862) in the wgagent session initialization function fails to properly enforce access controls on management API endpoints. An authenticated, low-privileged user can submit a specially crafted request to trigger denial of service (resource exhaustion/uncontrolled consumption) or arbitrary file read. The vulnerability requires valid authentication credentials but does not require elevated privileges, making it accessible to read-only or guest administrator accounts.
Affected products
- WatchGuard Fireware OS Default: 2026.3 before 2026.3.2, 2025.0 before 2026.2.3, 12.0 before 12.12.3; T15/T35: 12.0 before 12.5.21
Timeline
- 2026-09-29: disclosed
- 2026-09-29: patched: Fireware OS 2026.3.2, 2026.2.3, 12.12.3, 12.5.21