CVE-2026-36772
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 W3 Wireless Router v1.0.0.3(2204) was discovered to contain a stack overflow in the wl_radio parameter of the formwrlSSIDget 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 · moderate confidenceA stack-based buffer overflow vulnerability exists in the Tenda W3 Wireless Router (v1.0.0.3) within the formwrlSSIDget function. The overflow occurs when processing the wl_radio parameter, allowing an attacker to crash the device via crafted input, resulting in 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/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 device modelAccess the router admin interface or check the device label to confirm it is a Tenda W3 Wireless RouterAffected if Device is not a Tenda W3 router, then not affected by this specific CVE
-
Check firmware versionIn the router admin panel, navigate to System Settings or Firmware Upgrade section to view the current firmware version. Alternatively, check via telnet/SSH if enabled using 'cat /proc/version' or 'firmware_ver' commandAffected if Firmware version is 1.0.0.3(2204), then likely affected
-
Verify HTTP management interface is enabledCheck router network settings to confirm the web-based administration interface (HTTP/HTTPS) is enabled and accessible on LAN or WAN interfaceAffected if Web interface is disabled or blocked, the attack surface is reduced but the vulnerability still exists in the firmware code
-
Check for vulnerable formwrlSSIDget function exposureAttempt to access the router web interface and locate the wireless settings page that uses the wl_radio parameter. This function handles SSID configuration retrievalAffected if The formwrlSSIDget function handles the wl_radio parameter and accepts user input without length validation, making the device vulnerable when this parameter can be manipulated via HTTP requests
The device is affected if it is a Tenda W3 router running firmware v1.0.0.3(2204) with the HTTP management interface accessible, as the overflow occurs in the formwrlSSIDget function when an oversized wl_radio value is submitted.
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 dataInput validation and bounds checking should be implemented for the wl_radio parameter in the formwrlSSIDget function to prevent stack buffer overflow. If available, apply vendor firmware updates. Consider network segmentation to limit exposure to untrusted actors.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36772 — 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-36772 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