CVE-2026-6200
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 · uneditedA vulnerability was determined in Tenda F456 1.0.0.5. The affected element is the function formwebtypelibrary of the file /goform/webtypelibrary. This manipulation of the argument menufacturer/Go causes stack-based buffer overflow. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized.
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 Tenda F456 router firmware 1.0.0.5, specifically in the formwebtypelibrary function within /goform/webtypelibrary. The vulnerability is triggered via the 'menufacturer' or 'Go' parameter, allowing remote attackers to potentially execute arbitrary code via stack corruption.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 F456 router modelCheck the router label or login to the admin interface and look for the model number in the status or system information pageAffected if Device is not a Tenda F456 router - different models are not affected by this specific CVE
-
Check firmware version 1.0.0.5Log into the router web interface, navigate to System Settings or Firmware Upgrade page, and verify the firmware version displayed. Alternatively, check via telnet/SSH if available using 'cat /proc/version' or 'ver' commandAffected if Firmware version is not exactly 1.0.0.5 - other versions are not affected by this CVE
-
Verify web management interface is accessibleAttempt to access the router login page at http://[router-ip]/ using a browser. Check if the /goform/webtypelibrary endpoint responds (sends a request to http://[router-ip]/goform/webtypelibrary)Affected if Web interface is completely inaccessible from your network - exploitation requires access to this interface
-
Confirm remote web management is enabledIn the router admin interface, check under 'System Settings' or 'Remote Management' for an option like 'Remote Management' or 'Web Management from WAN'. Note the IP address or setting statusAffected if Remote management is enabled and the interface is exposed to untrusted networks - this increases exposure to remote exploitation
A user is affected if they own a Tenda F456 router running firmware version 1.0.0.5 with the web management interface accessible, especially from WAN if remote management is enabled.
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 dataImmediately restrict access to the router's web management interface from untrusted networks, disable remote web management if enabled, and monitor vendor for firmware updates addressing this vulnerability.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6200 — 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-6200 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