CVE-2026-36786
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 · uneditedShenzhen Tenda Technology Co., Ltd Tenda FH451 V1.0.0.9 was discovered to contain a stack overflow in the list1 parameter of the fromDhcpListClient function. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted HTTP request.
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 confidenceStack-based buffer overflow in Tenda FH451 router firmware V1.0.0.9 within the fromDhcpListClient function. The list1 HTTP parameter lacks proper bounds checking, allowing an attacker to overflow the stack and cause denial of service via crafted HTTP requests.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelAccess the router's web administration interface or check the device label to confirm the model is Tenda FH451Affected if Device is not a Tenda FH451 router, then not affected
-
Check firmware versionLog into the router web interface and navigate to System Status or Firmware Upgrade page to view the current firmware version; or use Nmap or curl to query the HTTP service and examine any version information in responsesAffected if Firmware version is not V1.0.0.9 (unpatched versions are vulnerable)
-
Confirm HTTP management interface is accessibleAttempt to reach the router's HTTP interface on common ports 80 or 8080 using a browser or curl command: curl http://<router-ip>/Affected if HTTP management interface is not reachable (internal network only or disabled)
-
Test for vulnerable parameter handlingSend an HTTP request to the router with an abnormally long list1 parameter to the fromDhcpListClient endpoint; for example: curl -X POST http://<router-ip>/goform/fromDhcpListClient -d "list1=AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA..." (adjust endpoint path based on actual router URLs)Affected if Request is processed without error or rejection of oversized input, indicating the vulnerability may be present
A Tenda FH451 router running firmware V1.0.0.9 with an exposed HTTP management interface is vulnerable; the list1 parameter must be processed by the fromDhcpListClient function for exploitation.
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 dataApply vendor firmware patch when available; until then, block external HTTP access to the router's web interface or implement network-level filtering to restrict malformed requests targeting the /fromDhcpListClient endpoint.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36786 — 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-36786 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