dbcve.org
F451 FirmwareOperating system · Tenda

CVE-2026-6135

HIGH · 8.8 CVSS v3.1 Published 2026-04-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
A weakness has been identified in Tenda F451 1.0.0.7_cn_svn7958. This issue affects the function fromSetIpBind of the file /goform/SetIpBind. Executing a manipulation of the argument page can lead to stack-based buffer overflow. The attack may be performed from remote. The exploit has been made available to the public and could be used for attacks.

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 · high confidence

A stack-based buffer overflow vulnerability exists in the Tenda F451 router firmware (version 1.0.0.7_cn_svn7958) within the /goform/SetIpBind form handler. The fromSetIpBind function fails to properly validate the length of the 'page' parameter before copying it to a fixed-size stack buffer, allowing an attacker to overwrite return addresses and potentially achieve remote code execution.

MitigationUpgrade router firmware to a patched version if available; otherwise, restrict access to the web management interface or disable remote administration to reduce attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
F451 FirmwareOperating system
Affected:= 1.0.0.7

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify router firmware version
    Access the router web management interface and navigate to System Settings > Firmware Upgrade, or check the label on the device bottom. Alternatively, use the command 'cat /proc/version' or 'cat /etc/os-release' if you have telnet/ssh access to the device.
    Affected if The firmware version is 1.0.0.7 (specifically build 1.0.0.7_cn_svn7958). Earlier or later versions are not affected by this specific CVE.
  2. Verify the specific firmware build
    Within the router admin panel, look for a build number, SVN revision, or hardware version field. This build is identified as 'cn_svn7958'. Compare this against the vendor release notes if available.
    Affected if The build string contains 'cn_svn7958', confirming this is the exact affected firmware version.
  3. Confirm web management interface is active
    Attempt to access http://[router-ip]/ from a browser. The login page should load. The vulnerable endpoint is at /goform/SetIpBind.
    Affected if The web interface responds and the /goform/SetIpBind endpoint is reachable (returns 200 or similar HTTP response, not 404). The vulnerability requires this web endpoint to be accessible.
  4. Check remote management configuration
    In the router admin panel, look for 'Remote Management', 'Remote Access', or 'Web Management' settings typically under Advanced or Security settings. Verify whether 'Remote Management' is enabled and note which IP addresses are allowed.
    Affected if Remote management is enabled with broad access (0.0.0.0/0 or wide subnet) rather than restricted to specific local IPs. This increases exposure to remote exploitation.

You are affected if your Tenda F451 runs firmware version 1.0.0.7 (build cn_svn7958) AND the /goform/SetIpBind web endpoint is accessible from the network where an attacker could send malicious 'page' parameter data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade router firmware to a patched version if available; otherwise, restrict access to the web management interface or disable remote administration to reduce attack surface.

Fix this in F451 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6135 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6135 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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