/

CVE-2026-34474

Severity:

HIGH RISK

(7.5)

Sensitive Data Exposure in ZTE ZXHN H298A/H108N Web

CVE-2026-34474

Awaiting Analysis

Vulnerability type

Category:

Sensitive Data Exposure

CWE:

CWE-200

Impact:

Credential Disclosure and Network Compromise

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Certain ZTE ZXHN H298A 1.1 and H108N 2.6 router firmware builds expose sensitive configuration data via crafted HTTP requests to the web management interface.

Under specific conditions, responses may contain the administrator password and WLAN pre‑shared key (PSK), or other device identifiers, allowing attackers to bypass authentication and compromise the local network.

Affected context

The issue occurs in the embedded web management interface of ZTE ZXHN H298A (1.1) and H108N (2.6) routers.

It manifests when the HTTP request routing and response generation logic return verbose configuration data to unauthenticated or weakly authenticated endpoints.

In vulnerable firmware builds, certain diagnostic, configuration, or status endpoints can be queried in ways that cause the device to serialize internal configuration structures directly into HTTP responses, sometimes including admin credentials or WLAN PSK.

Exposure may vary by build, with some versions leaking full credentials and others returning only partial identifiers such as serial numbers, ESSIDs, or MAC addresses.

Exploit preconditions

  • Attack surface: HTTP(S) web management interface of the router.
  • Required access:
  • Network reachability to the router's management interface (typically LAN, but sometimes WAN if remote management is enabled or misconfigured).
  • No valid credentials are strictly required if the vulnerable endpoint is improperly exposed to unauthenticated users.
  • Trigger point: Sending a crafted HTTP request (e.g., specific URI, parameters, or headers) that causes the router to return internal configuration data in the HTTP response.
  • Why exploitation is possible: The firmware exposes configuration data through web handlers that lack proper authorization checks and output filtering, causing sensitive internal fields (admin password, WLAN PSK, device identifiers) to be included in the serialized response.

Why this happens

This vulnerability stems from improper access control and data minimization in the router's web interface.

Internally, configuration state (including administrator passwords, WLAN PSK, and device identifiers) is stored in shared data structures used by both the configuration backend and the web UI.

Some HTTP handlers expose these structures directly—or via overly broad "dump" or status endpoints—without enforcing robust authentication and authorization checks.

Furthermore, responses are not filtered to remove or mask sensitive fields before being sent to the client.

This aligns with CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where systems disclose data that should remain confidential because they return more information than necessary or fail to restrict who can access it.

Potential impact

  • Attackers may obtain the router's administrator password and log into the management interface.
  • WLAN PSK leakage can enable unauthorized connection to the wireless network.
  • Compromise of the router's configuration, including DNS settings, port forwarding, and security options.
  • Facilitation of man-in-the-middle attacks, traffic interception, or redirection on the local network.
  • Use of exposed device identifiers (serial number, MAC, ESSID) for targeted attacks, social engineering, or device fingerprinting.
  • Potential pivoting to other devices on the LAN once network access or router admin control is obtained.

General mitigation guidance

Effective mitigation focuses on reducing exposure of sensitive data and tightening access to the management plane:

  • Restrict access to the router's web interface to trusted networks only (e.g., LAN-only access, disabling remote/WAN management where not strictly needed).
  • Enforce strong authentication and session handling for all endpoints that expose configuration-related data.
  • Apply the principle of least data: ensure HTTP responses only include the minimal non-sensitive data necessary for UI functionality, masking or omitting passwords, PSKs, and secret tokens.
  • Introduce strict server-side authorization checks per endpoint, preventing unauthenticated or low-privilege users from accessing configuration dumps or diagnostic data.
  • Segregate sensitive configuration storage from presentation logic so that web templates and handlers cannot automatically serialize secure fields.
  • Encourage operational hardening practices such as using strong, unique admin and WLAN credentials and rotating them after suspected exposure.
  • Where possible, segment management traffic from user traffic (e.g., using a wired management port or separate admin VLAN) to reduce who can reach the interface.

How teams detect issues like this

Organizations and security teams can look for this class of issue using:

  • Black-box testing:
  • Perform authenticated and unauthenticated HTTP enumeration of the router's web interface.
  • Capture responses (via proxies or automated scanners) and inspect them for the presence of passwords, PSKs, or other secrets in HTML, JSON, XML, or debug output.
  • Static/firmware analysis:
  • Analyze extracted firmware images for web application code (CGI binaries, Lua/PHP scripts, or proprietary handlers).
  • Identify endpoints that return configuration structures or call generic "dump" functions and verify whether they apply authentication and field-level filtering.
  • Code review signals:
  • Handlers that serialize entire configuration objects into responses without explicit whitelisting of non-sensitive fields.
  • Use of debug or diagnostic endpoints that expose internal state in cleartext.
  • Lack of role checks or authentication guards in routes handling status/configuration queries.
  • Policy and automated tooling:
  • Include sensitive-data scanning in CI/CD or firmware analysis pipelines, flagging responses or templates that contain password, key, or PSK fields.
  • Use web vulnerability scanners and DAST tools configured to search explicitly for credential strings and configuration secrets in responses.

Sources

SourceLink
gist.github.comgist.github.com/minanagehsalalma/7a8516b9b00d0008f2f25750320560c9
zte.com.cnzte.com.cn/global/
seclists.orgseclists.org/fulldisclosure/2026/May/20

Frequently asked

questions

It can be, but only if the router's management interface is exposed over the WAN (e.g., remote management enabled, misconfigured port forwarding, or ISP-managed access). If the interface is LAN-only, attackers typically must first gain access to the local network.

Not necessarily. The vulnerability arises because certain endpoints may fail to enforce authentication or authorization properly. In some builds, a network-adjacent attacker can send crafted requests without logging in and still receive sensitive data.

The most robust approach is to ensure that all management endpoints enforce strong authentication, and that responses only contain a carefully curated set of non-sensitive fields. Sensitive values (admin passwords, PSKs, keys) should never be returned by the web interface in cleartext, even to authenticated users.

Prevention relies on designing APIs with strict data minimization and access control:

  • Apply endpoint-level authorization and avoid generic configuration dump endpoints.
  • Use explicit whitelisting of response fields instead of serializing entire configuration objects.
  • Conduct regular security reviews and penetration testing of management interfaces.
  • Integrate automated checks for sensitive data exposure into development and firmware build pipelines.
Find out what's already
exploitable in your codebase.