CVE-2026-36800
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 a buffer overflow in the IPMacBindIndex parameter of the formIPMacBindDel 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 G0 router firmware v15.11.0.5 within the formIPMacBindDel function. The IPMacBindIndex parameter fails to properly validate input length before copying data into a fixed-size buffer, allowing an attacker to send a crafted HTTP request with an overly long parameter value to trigger the overflow and cause device 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 Tenda G0 router in your networkLocate network devices and identify if any are Tenda G0 routers by checking device model/firmware branding or SNMP/sysinfo responses showing vendor 'Tenda' and model 'G0'Affected if Device is a Tenda G0 router
-
Check installed firmware versionAccess router web interface or use 'grep' on firmware image for version string '15.11.0.5', or query /proc/mtd or bootlog for firmware version identifierAffected if Firmware version is 15.11.0.5 or earlier on a Tenda G0 device
-
Verify formIPMacBindDel endpoint existsProbe the router's web interface for the /goform/formIPMacBindDel endpoint using a HEAD or GET request, or inspect router firmware binary for the formIPMacBindDel function stringAffected if The formIPMacBindDel function is present in the firmware
-
Confirm IPMacBindIndex parameter is acceptedSend a benign HTTP POST request to /goform/formIPMacBindDel with a normal numeric value in the IPMacBindIndex parameter (e.g., IPMacBindIndex=1) and observe if the router processes itAffected if The endpoint accepts the IPMacBindIndex parameter without authentication failures
-
Check for crash logs or unusual behaviorReview router system logs, crash dumps, or watchdog logs for evidence of unexpected restarts or buffer overflow indicators around the time of the formIPMacBindDel requestsAffected if Device exhibits crashes or instability correlating with formIPMacBindDel endpoint access
You are affected if you operate a Tenda G0 router running firmware v15.11.0.5 or earlier and the formIPMacBindDel web endpoint is accessible on your network.
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 the vendor's latest firmware update for Tenda G0. If no update is available, restrict administrative interface access to trusted networks only using firewall rules to mitigate external exploitation.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36800 — 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-36800 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