# CVE-2026-13079: WatchGuard Mobile VPN with SSL Windows Client Local Privilege Escalation

> A local attacker can escalate privileges to SYSTEM on machines running the WatchGuard Mobile VPN with SSL Windows client.

- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jul 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-qgpj-9w2h-pcv3

## What is CVE-2026-13079?

CVE-2026-13079 is a high-severity vulnerability in Watchguard Fireware, published on 2 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A local privilege escalation vulnerability in the WatchGuard Mobile VPN with SSL client for Windows allows a local attacker to escalate their privileges to NT AUTHORITY\SYSTEM on the machine where the client is installed.

This issue affects the Mobile VPN with SSL client for Windows up to and including 2026.2.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 2 products.


Products: Watchguard Fireware, Watchguard Mobile Vpn With Ssl.

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

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

## Is CVE-2026-13079 being exploited?

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

## Other vulnerabilities in Watchguard Fireware

- [CVE-2022-26318](https://insights.sbomify.com/CVE-2022-26318/): WatchGuard Firebox and XTM Appliances Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-13079 is a high-severity vulnerability in Watchguard Fireware, published on 2 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-13079 in the wild and no public exploit code.

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-2026-13079/ (Markdown: https://insights.sbomify.com/CVE-2026-13079/index.md)
```

## Sources

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

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