# CVE-2026-19313: Fireware OS Pre-Authentication Heap Buffer Overflow in iked Allows Remote Code Execution

> Remote unauthenticated attackers can execute arbitrary code on WatchGuard Fireware OS devices via a heap buffer overflow in the iked process.

- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 11 Sep 2026
- **Also known as:** GHSA-w2pv-pjcj-h2vr

## What is CVE-2026-19313?

CVE-2026-19313 is a critical memory corruption vulnerability in WatchGuard Fireware OS, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An heap overflow vulnerability in the WatchGuard Fireware OS iked process allows a remote unauthenticated attacker to execute arbitrary code by sending specially crafted network traffic.

Weakness: CWE-680 (Integer Overflow to Buffer Overflow), CWE-190 (Integer Overflow or Wraparound), CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2026-19313?


## How do I fix CVE-2026-19313?

No fix has been published for CVE-2026-19313 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19313 being exploited?

There is no known exploitation of CVE-2026-19313 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19313 and fix it if it is affected.

What it is: CVE-2026-19313 is a critical memory corruption vulnerability in WatchGuard Fireware OS, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19313 in the wild and no public exploit code.

Affected product: WatchGuard Fireware OS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19313/ (Markdown: https://insights.sbomify.com/CVE-2026-19313/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19313
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19313
- OSV: https://osv.dev/vulnerability/CVE-2026-19313

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19313/
Summaries are generated and may contain mistakes; the official description above is the record.