CVE-2026-36793
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 multiple stack overflows in the formwrlSSIDset function via the mit_ssid and mis_ssid_index parameters. These vulnerabilities allow 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 confidenceStack buffer overflow vulnerability in Tenda W3 Wireless Router v1.0.0.3(2204) allows unauthenticated remote attackers to cause Denial of Service via specially crafted HTTP requests to the formwrlSSIDset function through the mit_ssid and mis_ssid_index parameters.
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.
-
Confirm Tenda W3 router modelAccess the router admin panel or check the device label to verify the model is Tenda W3Affected if The device is not a Tenda W3 router, then it is not affected by this specific CVE
-
Check firmware versionLog into the router web interface and navigate to System Settings > Firmware Upgrade or check the status page for the firmware version stringAffected if The installed firmware version is 1.0.0.3(2204) exactly, or falls within the v1.0.0.3(2204) release line, then it is likely affected
-
Verify web interface is accessibleAttempt to reach the router's HTTP/HTTPS management interface on the LAN IP (commonly 192.168.0.1)Affected if The web interface is reachable and responds to authentication requests, indicating the attack surface is present
-
Check wireless SSID configuration accessNavigate to Wireless Settings > Wireless SSID Configuration in the admin panel, or inspect if the formwrlSSIDset handler responds to requestsAffected if The wireless SSID configuration page is accessible or the formwrlSSIDset function is exposed, then the vulnerable code path can be reached
If the device is a Tenda W3 running firmware v1.0.0.3(2204) with an accessible web interface where wireless SSID settings can be configured, the environment is affected by this buffer overflow vulnerability.
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, restrict access to the router's web management interface to trusted networks only, disable remote administration if enabled, and monitor for anomalous traffic patterns.
- 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-36793 — 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-36793 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