# CVE-2026-34474: Information disclosure in n/a

> A crafted request to the ZTE router web interface exposes admin and WLAN credentials, enabling authentication bypass and network compromise.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 May 2026
- **Updated:** 26 May 2026
- **Also known as:** GHSA-ggh9-x7x7-xpw4

## What is CVE-2026-34474?

CVE-2026-34474 is a high-severity vulnerability in n/a, published on 6 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Sensitive data exposure leading to admin/WLAN credential leak in ZTE ZXHN H298A 1.1 and H108N 2.6. A crafted request to the router web interface can expose sensitive device and account information. In affected builds, the response may include the administrator password and WLAN PSK, enabling authentication bypass and network compromise. Some firmware versions may expose only partial identifiers (e.g., serial number, ESSID, MAC addresses).

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-34474 being exploited?

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

Public exploit code:

- CVE-2026-34474: unauthenticated ETHCheat=1 requests leak the admin password and Wi-Fi PSK from ZTE H298A/H108N routers. (github_poc): https://github.com/minanagehsalalma/cve-2026-34474-zte-h298a-h108n-sensitive-data-exposure
- ZTE H298A / H108N - Unauthenticated Credential Exposure (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34474 is a high-severity vulnerability in n/a, published on 6 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-34474 in the wild and no public exploit code.

Affected product: n/a. 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-34474/ (Markdown: https://insights.sbomify.com/CVE-2026-34474/index.md)
```

## Sources

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

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