CVE-2026-34474
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSensitive 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).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is an information disclosure vulnerability in ZTE ZXHN H298A (1.1) and H108N (2.6) routers where a specially crafted HTTP request to the web management interface returns sensitive credentials in the response, including the administrator password and WLAN Pre-Shared Key (PSK). The attack requires network access to the router's web interface but does not require prior authentication, making it highly exploitable.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the router modelCheck the device label on the router or log into the admin interface and look for the model number (typically displayed on the status or system info page)Affected if The device is a ZTE ZXHN H298A or H108N model
-
Check the firmware versionIn the router's web admin interface, navigate to Status or System Information page to find the firmware version. For H298A, look for version 1.1. For H108N, look for version 2.6Affected if The firmware version matches exactly H298A (1.1) or H108N (2.6)
-
Determine if the web management interface is network-accessibleFrom a remote system, attempt to access the router's HTTP interface (typically on port 80 or 8080) by entering the router's IP address in a web browserAffected if The web interface responds and is accessible from an untrusted network (not just from LAN)
-
Verify if the vulnerability is presentSend a crafted HTTP GET request to the router's web interface (e.g., to common endpoints like / Luci/ , /admin/ , or the login page) and observe if the response contains plaintext credentials such as admin password or WLAN PSK in the HTML or JSON responseAffected if The HTTP response contains sensitive credentials (administrator password or WLAN Pre-Shared Key) without having authenticated first
You are affected if you own a ZTE ZXHN H298A (firmware 1.1) or H108N (firmware 2.6) router and its web management interface is accessible from a network where untrusted users can send HTTP requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately restrict access to the router's web management interface from untrusted networks, disable remote WAN management if enabled, and contact ZTE for available firmware updates that address this credential exposure. Consider changing exposed credentials immediately if exploitation is suspected.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34474 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34474 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data