# CVE-2025-4106: WatchGuard Firebox leftover debug code vulnerability

> Authenticated admins can enable a diagnostic debug shell via leftover code, allowing unauthorized command execution and privilege escalation on Firebox devices.

- **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Oct 2025
- **Updated:** 8 Aug 2026
- **Also known as:** GHSA-23g2-f757-4428

## What is CVE-2025-4106?

CVE-2025-4106 is a high-severity vulnerability in WatchGuard Fireware OS, published on 24 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An authenticated admin user with access to both the management WebUI and command line interface on a Firebox can enable a diagnostic debug shell by uploading a platform and version-specific diagnostic package and executing a leftover diagnostic command.

Weakness: CWE-489 (Active Debug Code)

## Which versions are affected by CVE-2025-4106?


## How do I fix CVE-2025-4106?

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

## Is CVE-2025-4106 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-4106 and fix it if it is affected.

What it is: CVE-2025-4106 is a high-severity vulnerability in WatchGuard Fireware OS, published on 24 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-4106 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-2025-4106/ (Markdown: https://insights.sbomify.com/CVE-2025-4106/index.md)
```

## Sources

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

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