CVE-2026-36815
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 W15E v15.11.0.10 was discovered to contain a buffer overflow in the hostname parameter of the formSetNetCheckTools 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 Tenda W15E router firmware v15.11.0.10 within the formSetNetCheckTools function. The hostname parameter fails to properly validate input length before copying data into a fixed-size buffer, allowing an attacker to send a specially crafted HTTP request with an oversized hostname value to trigger the overflow and cause 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 admin interface (typically at 192.168.0.1) or check the physical device label to confirm the model is Tenda W15EAffected if Device is not a Tenda W15E router - different models are not affected by this specific vulnerability
-
Check firmware versionLog into the router web interface, navigate to System Settings or Status page, and locate the firmware version information. Compare against v15.11.0.10Affected if Firmware version matches exactly v15.11.0.10 - this is the affected version listed in the CVE
-
Verify web management interface is accessibleAttempt to access the router login page via HTTP (port 80 or 8080) from the network segment you want to assess. Confirm the web server responds.Affected if The web management interface is exposed and reachable - the attack requires sending HTTP requests to the formSetNetCheckTools function
-
Confirm formSetNetCheckTools function existsAttempt a POST request to the formSetNetCheckTools endpoint (commonly /goform/ or /cgi-bin/ on Tenda devices) - check if the endpoint accepts parametersAffected if The formSetNetCheckTools endpoint is accessible and accepts the hostname parameter - this is the vulnerable function
-
Check network exposure of management interfaceReview firewall rules, port forwarding settings, or WAN access configurations to determine if the web interface is accessible from untrusted networksAffected if The management interface is accessible from WAN or untrusted LAN segments - this increases exposure to remote attackers
You are affected if you have a Tenda W15E router running firmware version v15.11.0.10 with the web management interface accessible to the attacker.
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 updates when available; as a compensating control, restrict administrative interface access to trusted networks only or implement WAF/IPS rules to detect and block abnormally long hostname parameters in HTTP requests.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36815 — 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-36815 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