CVE-2025-14733: WatchGuard Firebox Out of Bounds Write Vulnerability

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

An Out-of-bounds Write vulnerability in the WatchGuard Fireware OS iked process may allow a remote unauthenticated attacker to execute arbitrary code. This vulnerability affects both the mobile user VPN with IKEv2 and the branch office VPN using IKEv2 when configured with a dynamic gateway peer. If the Firebox was previously configured with the mobile user VPN with IKEv2 or a branch office VPN using IKEv2 to a dynamic gateway peer, and both of those configurations have since been deleted, that Firebox may still be vulnerable if a branch office VPN to a static gateway peer is still configured.

Description quoted from the CVE record (assigned by WatchGuard, published 2025-12-19).

Weakness: CWE-787

How it can be exploited

Exploitable over the network with low attack complexity with no special attack requirements needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/U:Red

CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: yes. Technical impact: total.

On CISA KEV since
2025-12-19
US federal deadline
2025-12-26
Ransomware use
Yes

Public exploit evidence (Exploit Observer)

Also known as: BDU:2025-16142, EUVD-2025-204437, GHSA-hv82-jj64-jf47

VEDAS cluster: VEDAS:GAURCLOUD

Exploit Observer links 4 pieces of public exploit code or detection modules that name this CVE or one of its aliases.

Exploit code and modules (4)

Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.

Research and write-ups (1)

Vulnerability databases and vendor advisories (6)

Catalogue entries, not exploit evidence.

17 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS
0.294
likely to be attacked soon
VEDAS
0.971
strong exploit evidence
On CISA KEV
Yes, since 2025-12-19
Detection rule
None yet
EPSS (chance of attack)
10No cve-scores data 2026-02-22 to 2026-08-08no data0.1CVE-2025-14733 EPSS over time2025-122026-11-01
VEDAS (exploit evidence)
10No cve-scores data 2026-02-22 to 2026-08-08no data0.9CVE-2025-14733 VEDAS over time2025-122026-11-01

Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish.

Who is affected

ProductAffectedNot affected
WatchGuard Fireware OSfrom 2025.1 before 2025.1.4
from 12.0 before 12.11.6
from 11.10.2 up to and including 11.12.4+541730
Not stated
WatchGuard Fireware OSfrom 12.0 before 12.3.1+728352Not stated
WatchGuard Fireware OSfrom 12.0 before 12.5.15Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

Exploit Observer also maps it to: watchguard fireware, watchguard_technologies_inc. fireware_os.

How to fix it

Fixed versions stated in the CVE record: 2025.1.4, 12.11.6, 12.3.1+728352, 12.5.15.

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Vendor guidance:

How to detect it

There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.

References

Vendor advisories and patches

Government sources

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.