← Back to KEV catalog

CVE-2025-14733

Exploitation: active CVSS 9.3 CRITICAL Ransomware: known use

CVSS base score: 9.3 (Critical) vendor CNA · v4.0

Score assigned by the vendor's own CVE Numbering Authority (CNA); CISA's Vulnrichment program adds a score only when the CNA omits one. Vulnrichment source record →

WatchGuard Firebox Out of Bounds Write Vulnerability

Vendor: WatchGuard   Product: Firebox

Description

WatchGuard Fireware OS iked process contains an out of bounds write vulnerability in the OS iked process. This vulnerability may allow a remote unauthenticated attacker to execute arbitrary code and affects both the mobile user VPN with IKEv2 and the branch office VPN using IKEv2 when configured with a dynamic gateway peer.

Research & News Coverage

DateSourceArticle
2026-11-10 Kaspersky Securelist IT threat evolution in Q3 2026. Non-mobile statistics

Articles from monitored vendor research blogs and security news feeds that specifically mention this CVE. Coverage begins when feed monitoring started; earlier articles are not indexed.

Lifecycle Timeline

Each milestone comes from a different source, so gaps between them are gaps in what those sources publish, not evidence that nothing happened. EPSS history for this CVE holds 99 points from 2025-12-20, tracked daily from 2026-09-09; earlier points are weekly, which dates a spike to within a week. Peak probability 44.2% on 2026-02-28.

Published Applicability

CVE List v5 (CNA container) 5 affected · 0 fixed · 0 not affected

Check whether a specific version is affected →

What each source publishes about which product versions carry this vulnerability, kept as written rather than merged. Absence here means no source has published applicability data, not that nothing is affected.

Detection & Exploitation

Scan
none published
Exploit / Pen Test
Network IDS/IPS
none published
Host / SIEM
none published

Coverage across public collections only: Nuclei and OpenVAS NVT (scan); Snort and Suricata ET Open (network); Sigma and YARA (host/SIEM); Metasploit, Exploit-DB, public GitHub repositories and NVD exploit references (exploit). Absence here means nothing public was found, not that detection is impossible.
GitHub PoC repositories are collected automatically by PoC-in-GitHub (CC0) and filtered to repositories that are still online, contain code, and are starred or at least two weeks old. They are still not vetted: some are fakes and some are malware. Treat them as evidence that code was published, not as code to run.
NVD exploit references are links NVD's analysts tag as exploits; they confirm an exploit was referenced but carry no date. This product uses data from the NVD but is not endorsed or certified by the NVD.
OpenVAS coverage derives from the Greenbone Community Feed, made available under the Open Database License (ODbL) v1.0; its individual Vulnerability Tests are licensed GNU GPL v2.

First seenToolEvidenceEarliest reference
2025-12-23 GitHub PoC Unvetted — public repository machevalia/CVE-2025-14733

Metasploit is dated by the first commit of the module file, Exploit-DB by its publication date, and GitHub repositories by their creation date. GitHub PoC repositories are filtered (still online, contain code, starred or at least two weeks old) but not vetted: some are fakes and some are malware, so they show that code was published, not that it works or is safe to run. Evidence tiers are explained on the About page.

CISA Assessment (Vulnrichment / SSVC)

active
yes
total
—
9.3 CRITICAL
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
CWE-787 —
2025-12-19

Federal Remediation Window (BOD 26-04)

Yes — added 2025-12-19
yes
total control
If the asset isRemediate withinTable 1 row
Publicly exposed 3 days + forensic triage 1 of 16
Not publicly exposed 3 days + forensic triage 9 of 16

BOD 26-04 replaced the single KEV deadline of BOD 22-01 with four inputs: whether the asset is publicly exposed, KEV status, whether exploitation is automatable, and technical impact. Exposure belongs to each agency's asset, not to the CVE, so both outcomes are shown. Automatable and technical impact come from the CISA assessment above. Days are calendar days; for KEV entries the clock starts on the date it was added. Agencies make the final exposure call asset by asset, and may set shorter timelines.

D3FEND Countermeasures

Defensive techniques inferred by MITRE D3FEND from the underlying weakness (CWE-787) — general hardening and detection guidance for this weakness class, not a vendor patch for this specific CVE.

External References