CVE-2026-36801
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 IPMacBindRule parameter of the formIPMacBindAdd 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 confidenceBuffer overflow vulnerability in Tenda G0 router firmware v15.11.0.5 in the formIPMacBindAdd function's IPMacBindRule parameter allows remote attackers to cause denial of service via crafted HTTP requests.
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.
-
Confirm Tenda G0 router modelAccess router admin interface or check device label/marketing materials to verify the model is Tenda G0Affected if Device is not a Tenda G0 router - not affected
-
Check firmware versionLog into router admin panel (typically 192.168.0.1) and navigate to System Settings > Firmware Upgrade or Status page to view current firmware version; compare to v15.11.0.5Affected if Firmware version is v15.11.0.5 exactly - this is the affected version; versions higher/lower than 15.11.0.5 may have different affected status
-
Verify web interface is accessibleAttempt to access the router's HTTP management interface on the local network; check if port 80 or 443 is open externally via network scan (nmap -p 80,443 <router-ip>)Affected if Web interface is exposed to untrusted networks - increased attack surface for this vulnerability
-
Identify IP-MAC binding feature availabilityIn router admin panel, look for IP-MAC Binding, ARP Binding, or Access Control settings (usually under Security or Access Control menus); check if this feature is present in the firmwareAffected if IP-MAC binding feature exists and is configurable - vulnerable parameter IPMacBindRule is present in formIPMacBindAdd function
-
Check for DoS indicatorsReview router logs (System Log or Diagnostics page) for crashes, reboots, or service failures; monitor for unresponsive web interface or connectivity issuesAffected if Router exhibits unexpected crashes or DoS symptoms after potential exploitation attempts
Environment is affected if it is a Tenda G0 router running firmware v15.11.0.5 with the web interface accessible and the IP-MAC binding feature present, making the IPMacBindRule parameter in formIPMacBindAdd exploitable via crafted HTTP requests.
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 patch when available; as interim measures, restrict administrative interface access to trusted networks and implement input length validation on the affected parameter.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36801 — 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-36801 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