CVE-2026-36771
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 W3 Wireless Router v1.0.0.3(2204) was discovered to contain a stack overflow in the wl_radio parameter of the formwrlSSIDset function. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted input.
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 confidenceStack buffer overflow in the wl_radio parameter of the formwrlSSIDset function in Tenda W3 Wireless Router v1.0.0.3(2204) allows remote attackers to cause Denial of Service via crafted input exceeding expected parameter bounds.
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 the device modelAccess the router's web interface (typically http://192.168.0.1 or http://192.168.1.1) and navigate to the System Status or Device Information page to confirm the device is a Tenda W3 Wireless Router.Affected if The device is not a Tenda W3 router.
-
Check the firmware versionIn the router's web interface, go to System Status or Administration > Firmware Upgrade to view the installed firmware version. Compare it against v1.0.0.3(2204).Affected if The installed firmware version is v1.0.0.3(2204).
-
Verify the web management interface is accessibleAttempt to access the router's web interface from a remote network location (outside the local LAN). Confirm the HTTP/HTTPS management port is open on the WAN interface.Affected if The router's web interface is reachable from a remote network.
-
Check if remote administration is enabledIn the router's web interface, navigate to Advanced Settings > Remote Management (or similar). Determine if remote access via WAN is enabled.Affected if Remote administration is enabled and the web interface is accessible from WAN.
A user is affected if they are running Tenda W3 firmware v1.0.0.3(2204) and the router's web interface is accessible remotely (particularly with remote administration enabled).
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 patch when available; until then, restrict network access to router management interface via firewall and disable WAN management access.
- Consultation4.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 $3,584.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36771 — 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-36771 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