CVE-2026-36822
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 W20E v15.11.0.6 was discovered to contain a buffer overflow in the macAddr parameter of the formDelStaState 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 buffer overflow vulnerability exists in the macAddr parameter of the formDelStaState function in Tenda W20E router firmware v15.11.0.6. An unauthenticated remote attacker can send a crafted HTTP request with an oversized macAddr value to overflow the buffer, causing the device to crash and resulting in 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 device modelAccess the router web interface or check the device label to confirm the model is Tenda W20EAffected if Device model is Tenda W20E
-
Check firmware versionLog into the router admin panel and navigate to System Settings or Status page to view the firmware version; compare against v15.11.0.6Affected if Firmware version is 15.11.0.6 or falls within the affected version range
-
Verify HTTP management interface accessibilityCheck router firewall settings to determine if the web management interface (HTTP/HTTPS ports) is accessible from external networks or untrusted IPsAffected if Remote HTTP management is enabled and exposed to untrusted networks
-
Inspect for crash logs or device instabilityReview system logs or uptime status for unexplained reboots, crash dumps, or frequent device resets occurring without user interventionAffected if Device exhibits unexpected crashes or reboots that correlate with external HTTP requests
-
Review HTTP request loggingCheck router access logs for unusually long macAddr parameter values in formDelStaState POST requests originating from external sourcesAffected if Logs show long macAddr values in formDelStaState requests from untrusted IPs
The device is affected if it is a Tenda W20E running firmware v15.11.0.6 (or affected version) with its HTTP management interface exposed to untrusted networks.
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 any vendor-supplied firmware update for the Tenda W20E. If no update is available, restrict network access to the router's management interface using firewall rules or VLAN segmentation to prevent unauthorized HTTP requests.
- Consultation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,296.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36822 — 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-36822 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