# CVE-2026-93862: Fireware OS Out-of-Bounds Read in FireCluster Sync Allows Denial of Service


- **Severity:** High 7.2 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-vq3j-9jcw-wpfh

## What is CVE-2026-93862?

CVE-2026-93862 is a high-severity vulnerability in WatchGuard Fireware OS, published on 27 Oct 2026. 

### Official description

An out-of-bounds read vulnerability in the FireCluster Sync processing allows an attacker positioned on the cluster interconnect, such as a compromised cluster peer or an on-path network attacker, to repeatedly crash the firewall's cluster synchronization process by sending specially crafted network traffic, resulting in a sustained denial of service.

Weakness: CWE-787 (Out-of-bounds Write), CWE-823 (Use of Out-of-range Pointer Offset), CWE-129 (Improper Validation of Array Index), CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-93862 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93862 is a high-severity vulnerability in WatchGuard Fireware OS, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-93862 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-93862/ (Markdown: https://insights.sbomify.com/CVE-2026-93862/index.md)
```

## Sources

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

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