WatchGuard Fireware OS up to 12.5.18/12.12/2026.2 Fireware Management Web UI deserialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.72+ |
Summary
A vulnerability classified as problematic has been found in WatchGuard Fireware OS up to 12.5.18/12.12/2026.2. Affected by this issue is some unknown functionality of the component Fireware Management Web UI. The manipulation leads to deserialization. This vulnerability is referenced as CVE-2026-13371. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in WatchGuard Fireware OS up to 12.5.18/12.12/2026.2 and classified as problematic. This issue affects some unknown processing of the component Fireware Management Web UI. The manipulation with an unknown input leads to a deserialization vulnerability. Using CWE to declare the problem leads to CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. Impacted is availability. The summary by CVE is:
An authenticated administrator can trigger a denial-of-service condition in the Fireware Management Web UI by sending malformed or crafted data to the put_data endpoint, which performs unsafe deserialization of the attacker-supplied input.
The weakness was published by Cody Sixteen as wgsa-2026-00014. The advisory is shared at watchguard.com. The identification of this vulnerability is CVE-2026-13371 since 06/25/2026. The exploitation is known to be easy. The attack may be initiated remotely. The exploitation requires an enhanced level of successful authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/03/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 12.0
- 12.1
- 12.2
- 12.3
- 12.4
- 12.5
- 12.5.0
- 12.5.1
- 12.5.2
- 12.5.3
- 12.5.4
- 12.5.5
- 12.5.6
- 12.5.7
- 12.5.8
- 12.5.9
- 12.5.10
- 12.5.11
- 12.5.12
- 12.5.13
- 12.5.14
- 12.5.15
- 12.5.16
- 12.5.17
- 12.5.18
- 12.6
- 12.7
- 12.8
- 12.9
- 12.10
- 12.11
- 12.12
- 2026.0
- 2026.1
- 2026.2
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.9VulDB Meta Temp Score: 4.9
VulDB Base Score: 4.9
VulDB Temp Score: 4.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: DeserializationCWE: CWE-502 / CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
06/25/2026 CVE reserved07/03/2026 Advisory disclosed
07/03/2026 VulDB entry created
07/03/2026 VulDB entry last update
Sources
Advisory: wgsa-2026-00014Researcher: Cody Sixteen
Status: Confirmed
CVE: CVE-2026-13371 (🔒)
GCVE (CVE): GCVE-0-2026-13371
GCVE (VulDB): GCVE-100-376025
Entry
Created: 07/03/2026 06:23Changes: 07/03/2026 06:23 (66)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.