dbcve.org
F451 FirmwareOperating system · Tenda

CVE-2026-6134

HIGH · 8.8 CVSS v3.1 Published 2026-04-12
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 security flaw has been discovered in Tenda F451 1.0.0.7_cn_svn7958. This vulnerability affects the function fromqossetting of the file /goform/qossetting. Performing a manipulation of the argument qos results in stack-based buffer overflow. The attack is possible to be carried out remotely. The exploit has been released to the public and may 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

Stack-based buffer overflow in Tenda F451 router's QoS settings handler (fromqossetting function in /goform/qossetting). The qos parameter is not properly bounds-checked before being copied to a stack buffer, allowing remote attackers to overflow the stack and potentially execute arbitrary code via the publicly available exploit.

MitigationDisable remote WAN access to the router's web interface immediately. Apply vendor firmware updates when available. If no update exists, replace the device or implement strict network segmentation to prevent internet-facing exposure.

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. Confirm Tenda F451 router model and firmware version
    Access the router's web administration interface (typically at 192.168.0.1 or 192.168.1.1) and navigate to System Settings or Firmware Upgrade to view the current firmware version. Alternatively, use the command 'grep -i version /etc/*release' or inspect the firmware file if you have shell access via telnet/SSH.
    Affected if The displayed firmware version is exactly 1.0.0.7
  2. Identify if the vulnerable QoS handler is present
    Check for the existence of the /goform/qossetting endpoint by examining the router's web server configuration or by attempting to access http://[router-ip]/goform/qossetting. If the router firmware binary is available, search for the 'fromqossetting' string in the binary.
    Affected if The /goform/qossetting endpoint responds to requests or the 'fromqossetting' function is found in the firmware binary
  3. Verify WAN accessibility of the router's web interface
    From an external network (or using an online port scanner), check if TCP ports 80 or 443 on the router's public IP address are open and responding. Log into the router admin panel and check under 'Advanced' or 'Remote Management' for any WAN access enabled settings.
    Affected if The router's web interface (HTTP/HTTPS on ports 80/443) is accessible from the WAN/internet
  4. Check for exposed QoS configuration parameters
    Send a crafted POST request to /goform/qossetting with an overly long string in the 'qos' parameter (e.g., qos=A*500) and observe if the router crashes or behaves unexpectedly. Alternatively, capture and analyze network traffic to identify any existing QoS configuration submissions.
    Affected if The router accepts and processes QoS settings via the /goform/qossetting endpoint with the 'qos' parameter, indicating the vulnerable code path is present

A user is affected if they are running Tenda F451 firmware version 1.0.0.7 AND the router's web interface is accessible (either locally or via WAN) with the QoS settings handler active.

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

Disable remote WAN access to the router's web interface immediately. Apply vendor firmware updates when available. If no update exists, replace the device or implement strict network segmentation to prevent internet-facing exposure.

Fix this in F451 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Check whether your project pulls in CVE-2026-6134 — 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-6134 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