dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2026-34473

HIGH · 7.5 CVSS v3.1 Published 2026-05-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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 DoS in ZTE H8102E, H168N, H167A, H199A, H288A, H198A, H267A, H267N, H268A, H388X, H196A, H369A, H268N, H208N, H367N, H181A, and H196Q. A denial-of-service condition can be triggered against the router's web interface by sending an oversized application/x-www-form-urlencoded POST body. After triggering, the management interface may become unresponsive until the device is rebooted. This may affect any firmware version prior to 2022 (reporter observation). The supplier stated that devices are not vulnerable since 2021-03-23; operator firmware may vary.

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 denial-of-service vulnerability in ZTE H8102E, H168N, H167A, and 13 other router models. Attackers can crash the management interface by sending an oversized application/x-www-form-urlencoded POST body, rendering the web interface unresponsive until device reboot.

MitigationVerify firmware version on affected devices and apply vendor updates released after 2021-03-23; network segmentation and firewall rules can limit exposure to unauthenticated attackers.

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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 your ZTE router model
    Check the device label or web interface footer for the exact model number (e.g., H8102E, H168N, H167A)
    Affected if Model is H8102E, H168N, H167A, or any of the 13 other affected ZTE router models
  2. Determine firmware version
    Access the router web interface, navigate to Status or Device Info page, and record the firmware version string
    Affected if Firmware version is older than the vendor fix released after 2021-03-23 (compare your version to the affected range for your specific model)
  3. Verify web management interface is enabled
    Check router settings under Advanced or Administration for HTTP/HTTPS management service status
    Affected if Web-based management interface is enabled and accessible
  4. Confirm network exposure
    Determine if the management interface is reachable from WAN/untrusted networks (check firewall rules, port forwarding, or remote management settings)
    Affected if The management web interface is exposed to unauthenticated network attackers (WAN side)
  5. Test for DoS condition
    Send a large application/x-www-form-urlencoded POST request to the router's login or configuration endpoint using a tool like curl or Burp Suite with an oversized body (e.g., >10KB of data)
    Affected if The router web interface becomes unresponsive or crashes after receiving the oversized POST request

You are affected if your ZTE router model matches H8102E, H168N, H167A, or related models, your firmware predates the fix, and the management interface is network-accessible to unauthenticated attackers.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Verify firmware version on affected devices and apply vendor updates released after 2021-03-23; network segmentation and firewall rules can limit exposure to unauthenticated attackers.

Recommended fix Moderate confidence

Latest available firmware for each specific model (post-2021-03-23 release) from ZTE or ISP provider

  1. Identify the exact model number of the ZTE router from the affected list (H8102E, H168N, H167A, H199A, H288A, H198A, H267A, H267N, H268A, H388X, H196A, H369A, H268N, H208N, H367N, H181A, or H196Q)
  2. Navigate to ZTE's official support portal at www.zte.com.cn or the ISP-specific firmware download page
  3. Locate the firmware download section for the specific router model
  4. Download the latest available firmware version (firmware released on or after March 23, 2021 contains the fix)
  5. Access the router's web management interface via its default IP address (typically 192.168.1.1 or 192.168.0.1)
  6. Navigate to the Administration or System Tools section
  7. Locate the firmware upgrade or backup/restore option
  8. Upload the downloaded firmware file and initiate the upgrade process
Caveat Standard firmware upgrade risks apply - ensure stable power during upgrade to avoid brick; some ISP-customized firmware may have different update mechanisms

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34473 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-34473 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