# CVE-2026-6373: Sensitive Data Exposure in Zyxel WAH7601 Router

> Attackers can obtain sensitive system information from Zyxel WAH7601 routers, facilitating web application fingerprinting and potential further attacks.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 20 Aug 2026
- **Also known as:** GHSA-3hwg-rq85-p4mc

## What is CVE-2026-6373?

CVE-2026-6373 is a medium-severity vulnerability in Zyxel Networks WAH7601, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Exposure of sensitive system information to an unauthorized control sphere vulnerability in Zyxel Networks WAH7601 allows Web Application Fingerprinting.

This issue affects WAH7601: through 20072026.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

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


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

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

## Is CVE-2026-6373 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6373 is a medium-severity vulnerability in Zyxel Networks WAH7601, published on 10 Aug 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-6373 in the wild and no public exploit code.

Affected product: Zyxel Networks WAH7601. 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-6373/ (Markdown: https://insights.sbomify.com/CVE-2026-6373/index.md)
```

## Sources

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

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