# CVE-2022-26318: WatchGuard Firebox and XTM Appliances Arbitrary Code Execution

> Unauthenticated attackers can execute arbitrary code on WatchGuard Firebox and XTM appliances, requiring immediate firmware upgrades.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 25 Mar 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Mar 2022
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-vvw7-v96v-gmxr

## What is CVE-2022-26318?

CVE-2022-26318 is a critical code injection vulnerability in Watchguard Fireware, published on 4 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

On WatchGuard Firebox and XTM appliances, an unauthenticated user can execute arbitrary code, aka FBX-22786. This vulnerability impacts Fireware OS before 12.7.2_U2, 12.x before 12.1.3_U8, and 12.2.x through 12.5.x before 12.5.9_U2.

## Which versions are affected by CVE-2022-26318?

It affects 1 product.


Products: Watchguard Fireware.

## How do I fix CVE-2022-26318?

No fix has been published for CVE-2022-26318 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 15 Apr 2022.

## Is CVE-2022-26318 being exploited?

Yes. Attackers have exploited CVE-2022-26318 in the wild since at least 25 Mar 2022.

Public exploit code:

- https://github.com/misterxid/watchguard_cve-2022-26318 (github_poc): https://github.com/misterxid/watchguard_cve-2022-26318
- Watchguard RCE POC CVE-2022-26318 (github_poc): https://github.com/h3llk4t3/Watchguard-RCE-POC-CVE-2022-26318
- https://github.com/BabyTeam1024/CVE-2022-26318 (github_poc): https://github.com/BabyTeam1024/CVE-2022-26318
- WatchGuard XTM Firebox Unauthenticated Remote Command Execution (metasploit)
- PoC for Watchguard CVE-2022-26318 updated to Python3.12 (github_poc): https://github.com/egilas/Watchguard-RCE-POC-CVE-2022-26318

## Other vulnerabilities in Watchguard Fireware

- [CVE-2025-14733](https://insights.sbomify.com/CVE-2025-14733/): WatchGuard Firebox Out of Bounds Write (critical 9.3, exploited in the wild)
- [CVE-2025-9242](https://insights.sbomify.com/CVE-2025-9242/): WatchGuard Firebox Out-of-Bounds Write (critical 9.3, exploited in the wild)
- [CVE-2022-23176](https://insights.sbomify.com/CVE-2022-23176/): WatchGuard Firebox and XTM Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2022-31789](https://insights.sbomify.com/CVE-2022-31789/): Integer overflow in n/a (critical 9.8)
- [CVE-2013-6021](https://insights.sbomify.com/CVE-2013-6021/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-26318 and fix it if it is affected.

What it is: CVE-2022-26318 is a critical code injection vulnerability in Watchguard Fireware, published on 4 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2022-26318 in the wild since at least 25 Mar 2022.

Affected product: Watchguard Fireware. 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-2022-26318/ (Markdown: https://insights.sbomify.com/CVE-2022-26318/index.md)
```

## Sources

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

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