CVE-2026-36798
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 G0 v15.11.0.5 was discovered to contain multiple stack overflows in the formSetDebugCfgr function via the enable, level, and module 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 G0 router firmware v15.11.0.5 where the formSetDebugCfgr function fails to validate input length for the enable, level, and module HTTP parameters, allowing crafted requests to overflow the stack 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Tenda G0 firmware versionAccess the router web interface and navigate to System Settings or Status page to view the firmware version, or use telnet/SSH to connect and run 'version' or 'cat /proc/version' if availableAffected if The firmware version is v15.11.0.5 exactly or falls within an unpatched version range prior to the fix
-
Confirm web management interface is accessibleAttempt to reach the router IP via HTTP (port 80) or HTTPS (port 443) from a client on the networkAffected if The router web interface responds to HTTP/HTTPS requests, indicating the management interface is enabled and network-accessible
-
Identify if formSetDebugCfgr endpoint is exposedSend a crafted HTTP POST request to the router with the path or parameter associated with formSetDebugCfgr, typically found in the web interface forms or by inspecting firmware binary for this function nameAffected if The router accepts requests to the formSetDebugCfgr function and processes the enable, level, or module parameters
-
Check if debug or configuration features are enabledInspect the router web interface for debug, logging, or configuration settings that may expose the vulnerable parameters, or examine HTTP responses when interacting with the routerAffected if Debug configuration features are accessible or the enable/level/module parameters can be set via HTTP requests without authentication safeguards
-
Verify the device is processing user input without bounds checkingSend a test HTTP POST request with abnormally long strings in the enable, level, or module parameters and observe for unexpected behavior, crashes, or service interruptionAffected if Long input in these parameters causes denial of service, crash, or abnormal router behavior indicating a stack overflow condition
The environment is affected if the Tenda G0 router runs firmware v15.11.0.5 (or an unpatched version) and has the web management interface accessible with the formSetDebugCfgr function and its enable/level/module parameters exposed to user input.
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 dataUpdate to a patched firmware version if available; otherwise, implement input length validation in the formSetDebugCfgr function or deploy a WAF/IPS to filter malicious requests targeting the vulnerable endpoint.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36798 — 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-36798 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