How severe is CVE-2025-14733?

No CVSS score has been assigned to CVE-2025-14733 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-14733?

Affected package information for CVE-2025-14733 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2025-14733?

No fixed release is recorded for CVE-2025-14733 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2025-14733 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2025-14733 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is CVE-2025-14733 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-14733 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-14733?

CVE-2025-14733 has an EPSS (Exploit Prediction Scoring System) score of 26.5%, placing it in the 98th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

Is CVE-2025-14733 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2025-14733 (WatchGuard Firebox Out of Bounds Write Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-12-19. CISA required all US federal civilian agencies to remediate this vulnerability by 2025-12-26. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2025-14733?

CVE-2025-14733 is classified as Out-of-bounds Write (CWE-787). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-14733 published, and has it been updated?

CVE-2025-14733 was published on December 19, 2025 and was last updated on September 9, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV · ACTIVELY EXPLOITED

CVE-2025-14733

CVE-2025-14733 is a Out-of-bounds Write vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2025-12-19) and has been used in ransomware campaigns — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

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…

Published

Dec 19, 2025

Updated

Sep 9, 2026

Affected

1 product

Patched

See advisory

Exploits

None indexed

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2025-12-19 — including use in ransomware campaigns. Federal agencies were required to remediate by 2025-12-26.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2025-14733.

EPSS Exploitation Probability

via FIRST.org ↗

26.5%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

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.

Affected Products

1 product · 3 configurations

firewarewatchguard

≥ 2025.1 && < 2025.1.4

range

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2025-14733 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2025-14733 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works