Zxhn H188a FirmwareOperating system · Zte

CVE-2026-34472

HIGH · 7.1 CVSS v3.1 Published 2026-03-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
76/100
Remediation priority · High
No privileges Zero-click

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 · unedited
Unauthenticated credential disclosure in the wizard interface in ZTE ZXHN H188A V6.0.10P2_TE and V6.0.10P3N3_TE allows unauthenticated attackers on the local network to retrieve sensitive credentials from the router's web management interface, including the default administrator password, WLAN PSK, and PPPoE credentials. In some observed cases, configuration changes may also be performed without authentication.

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 · high confidence

Unauthenticated credential disclosure vulnerability in the web management wizard interface of ZTE ZXHN H188A routers (V6.0.10P2_TE and V6.0.10P3N3_TE) allows local network attackers to retrieve sensitive credentials including default admin password, WLAN PSK, and PPPoE credentials without authentication, and in some cases perform configuration changes.

MitigationApply vendor firmware update when available; immediately change default administrator password, WLAN PSK, and PPPoE credentials; disable remote management access and restrict local network access to trusted devices only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Zxhn H188a FirmwareOperating system
Affected:= 6.0.10p2_te= 6.0.10p3n3_te

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the router model
    Access the router's web interface or check the device label to confirm the model is ZTE ZXHN H188A
    Affected if The device is not a ZTE ZXHN H188A model, then it is not affected by this specific CVE
  2. Check the firmware version
    Log into the router web interface and navigate to the status or system information page to view the firmware version, or use the command line and check the /etc/version file or similar
    Affected if The firmware version is either 6.0.10p2_te or 6.0.10p3n3_te, then the device is vulnerable
  3. Verify web management interface accessibility
    Attempt to access the router web interface by entering the router IP address (commonly 192.168.1.1) in a web browser from a device on the local network
    Affected if The web management interface is reachable from the local network without authentication, the vulnerability could be exploited
  4. Check if default admin password is unchanged
    Attempt to log into the web interface using the default admin username and password (typically admin/admin or admin/password)
    Affected if The default admin credentials still work, the device may be vulnerable and the default password may be retrievable via the flaw

The device is affected if it is a ZTE ZXHN H188A router running firmware version 6.0.10p2_te or 6.0.10p3n3_te with the web management interface accessible on the local network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware update when available; immediately change default administrator password, WLAN PSK, and PPPoE credentials; disable remote management access and restrict local network access to trusted devices only.

Fix this in Zxhn H188a Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34472 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34472 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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