CVE-2026-36785
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 page 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 · moderate confidenceA stack-based buffer overflow vulnerability exists in the Tenda FH451 router firmware V1.0.0.9 within the fromDhcpListClient function. The page parameter in HTTP requests is not properly bounds-checked before being copied to a stack buffer, allowing an attacker to overwrite stack memory via crafted requests and trigger a denial of service.
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 router modelAccess the router admin interface or check the device label to confirm the model is Tenda FH451.Affected if The device model is Tenda FH451.
-
Check firmware versionLog into the router admin panel and navigate to System Status or Firmware Upgrade page to view the installed firmware version. Compare against V1.0.0.9.Affected if The installed firmware version is V1.0.0.9.
-
Verify web interface exposureDetermine if the router's HTTP administrative interface is accessible from external/untrusted networks by checking WAN access settings in the router's firewall or remote management configuration.Affected if The router web interface is reachable from untrusted networks.
-
Check remote management statusIn the router admin panel, look for Remote Management, Remote Access, or WAN Management settings and verify whether HTTP/HTTPS remote access is enabled.Affected if Remote management via HTTP/HTTPS is enabled and accessible from WAN.
-
Confirm DhcpListClient function accessibilitySend a test HTTP request to the router's public IP targeting the endpoint that contains the fromDhcpListClient function (if known) or attempt to access the DHCP client list page via the web interface.Affected if The DHCP client list feature or related page is accessible without authentication.
The device is affected if it is a Tenda FH451 router running firmware V1.0.0.9 with its web interface or remote management feature exposed to untrusted networks, allowing unauthenticated attackers to send crafted requests to the fromDhcpListClient function.
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 dataUpgrade the Tenda FH451 firmware to a patched version if available. If no patch exists, implement input validation and length checks on the page parameter in the fromDhcpListClient function, or restrict access to the affected HTTP endpoint.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36785 — 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-36785 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