CVE-2026-36770
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 US_W3V1.0BR v1.0.0.3 was discovered to contain a stack overflow in the Go parameter of the ask_to_reboot 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 · high confidenceA stack buffer overflow vulnerability exists in the Tenda US_W3V1.0BR router firmware v1.0.0.3. The vulnerability is in the 'ask_to_reboot' function where the 'Go' parameter is not properly validated before being copied to a stack-based buffer, allowing an attacker to overflow the stack and cause 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 the router modelAccess the router's web administration interface or check the device label/marketing to confirm the model is Tenda US_W3V1.0BRAffected if The device is a Tenda US_W3V1.0BR router
-
Check the firmware versionLog into the router's web interface (typically at 192.168.0.1 or 192.168.1.1) and navigate to System Settings or Status page to view the firmware version; alternatively, check via telnet/SSH if enabledAffected if The firmware version is 1.0.0.3 (exact match to the affected version)
-
Verify the ask_to_reboot endpoint existsSend a GET request to common Tenda endpoints (such as /goform/ or /cgi/) to enumerate available forms and identify if ask_to_reboot is exposed; this typically appears as /goform/ask_to_rebootAffected if The /goform/ask_to_reboot endpoint is accessible via HTTP/HTTPS without authentication
-
Confirm the Go parameter is acceptedSend a POST request to the ask_to_reboot endpoint with a test 'Go' parameter value (such as 'test') and observe if the parameter is processed without sanitization errorsAffected if The router accepts and processes the 'Go' parameter without rejecting unusual input
A user is affected if they own a Tenda US_W3V1.0BR router running firmware version 1.0.0.3 with the ask_to_reboot web endpoint publicly or internally accessible.
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 dataImplement proper input validation and bounds checking on the 'Go' parameter before copying to the stack buffer. If available, apply vendor firmware updates. As a temporary workaround, restrict access to the affected management interface.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36770 — 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-36770 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