CVE-2026-36783
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 O3 Wireless Router v1.0.0.5(4180) was discovered to contain a stack overflow in the domain parameter of the fromNetToolGet 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 confidenceStack-based buffer overflow in the fromNetToolGet function of Tenda O3 Wireless Router v1.0.0.5(4180). The domain parameter in HTTP requests is not properly bounds-checked, allowing attackers to overflow the stack buffer via crafted requests 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.
-
Confirm Tenda O3 router modelAccess the router web interface or check the device label/marketing to identify the exact model. Look for 'O3' in the product name or model number.Affected if The device is not a Tenda O3 Wireless Router
-
Check firmware versionLog into the router web management interface and navigate to System Settings or Status page to view the firmware version. Alternatively, check via telnet/SSH if available.Affected if Firmware version is 1.0.0.5 (exact match to the affected version)
-
Verify web management interface is enabledCheck router admin settings to confirm the HTTP/HTTPS web management interface is turned on. Look for 'Web Management' or 'Remote Management' settings.Affected if The web management interface is accessible on HTTP (port 80) or HTTPS (port 443)
-
Check if fromNetToolGet endpoint is reachableSend a crafted HTTP GET/POST request to the router with a malformed or missing 'domain' parameter to the endpoint that handles fromNetToolGet. This typically requires access to the router locally or via VPN since remote management may be disabled.Affected if The router responds to requests targeting the fromNetToolGet function (request completes without being blocked by authentication or network restrictions)
The device is affected if it is a Tenda O3 router running firmware version 1.0.0.5 with the web management interface accessible and the fromNetToolGet endpoint exposed.
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 update when available; if no update exists, consider network segmentation or device replacement. Implement WAF/IPS rules to filter abnormally large domain parameter values destined for the router's web interface.
- Consultation4.0 h
- Implementation2.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36783 — 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-36783 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