How severe is CVE-2025-9242?

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

Which packages are affected by CVE-2025-9242?

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

How do I fix CVE-2025-9242?

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

How do I detect CVE-2025-9242 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-9242 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-9242 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2025-9242, including . All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

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

CVE-2025-9242 has an EPSS (Exploit Prediction Scoring System) score of 91.8%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

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

Yes. CVE-2025-9242 (WatchGuard Firebox Out-of-Bounds Write Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-11-12. CISA required all US federal civilian agencies to remediate this vulnerability by 2025-12-03. 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. 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-9242?

CVE-2025-9242 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-9242 published, and has it been updated?

CVE-2025-9242 was published on September 17, 2025 and was last updated on August 10, 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-9242 — Watchtowrlabs

CVE-2025-9242 is a Out-of-bounds Write vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2025-11-12) — 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

Sep 17, 2025

Updated

Aug 10, 2026

Affected

1 product

Patched

See advisory

Exploits

1 known

Exploitation data as of Oct 23, 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-11-12. Federal agencies were required to remediate by 2025-12-03.
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-9242.

EPSS Exploitation Probability

via FIRST.org ↗

91.8%probability of exploitation in next 30 days

Very High Risk+0.50%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

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

Description

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.

Affected Products

1 product · 3 configurations

firewarewatchguard

≥ 11.10.2 && < 12.5.13

1 version

2025.1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

watchtowrlabs/watchTowr-vs-WatchGuard-CVE-2025-9242

⭐ 13🍴 5Mar 2026

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-9242 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

O3 Security · Impact-Aware SCA

Is CVE-2025-9242 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works