dbcve.org
F451 FirmwareOperating system · Tenda

CVE-2026-6122

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 vulnerability has been found in Tenda F451 1.0.0.7. Affected by this issue is the function frmL7ProtForm of the file /goform/L7Prot of the component httpd. Such manipulation of the argument page leads to stack-based buffer overflow. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

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 httpd service. The frmL7ProtForm function in /goform/L7Prot fails to properly validate the 'page' parameter before using it in a stack-based buffer, allowing remote attackers to potentially execute arbitrary code via crafted HTTP requests.

MitigationApply vendor firmware patch if available; otherwise restrict access to the httpd service (port 80/443) or disable the L7Prot functionality until a fix is released. Consider network segmentation to limit 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. Identify the installed firmware version
    Access the Tenda F451 web management interface (usually at 192.168.0.1) and navigate to System Settings > Firmware Version, or check via CLI using 'cat /proc/version' or 'ver' command if SSH/telnet is available
    Affected if The firmware version is exactly 1.0.0.7
  2. Confirm the httpd component is running
    If you have shell access, run 'ps | grep httpd' or 'ps aux | grep httpd' to verify the httpd process is active
    Affected if The httpd process is running and serving the web interface
  3. Verify the /goform/L7Prot endpoint is reachable
    Attempt to access the endpoint by sending a request to http://[device-ip]/goform/L7Prot using curl or a browser. A valid response (even an error page) indicates the endpoint exists and is enabled
    Affected if The endpoint responds to HTTP requests, meaning it is accessible and not disabled by network filtering
  4. Test if the 'page' parameter is accepted
    Send a GET or POST request to /goform/L7Prot with a 'page' parameter (e.g., curl 'http://192.168.0.1/goform/L7Prot?page=test'). Observe whether the device processes the parameter without rejecting it
    Affected if The device accepts and processes the 'page' parameter without rejecting it, indicating the vulnerable code path is reachable

You are affected if the firmware version is exactly 1.0.0.7 AND the httpd service is running with the /goform/L7Prot endpoint accessible and accepting the 'page' parameter.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware patch if available; otherwise restrict access to the httpd service (port 80/443) or disable the L7Prot functionality until a fix is released. Consider network segmentation to limit exposure.

Recommended fix Moderate confidence

Any firmware version newer than 1.0.0.7 that includes the security fix for the /goform/L7Prot stack-based buffer overflow (check Tenda's release notes)

  1. 1. Visit the official Tenda support website at www.tenda.com.cn to check for firmware updates for the F451 device.
  2. 2. Look for firmware versions newer than 1.0.0.7 that address security vulnerabilities.
  3. 3. Download the latest firmware version available from Tenda's official support page.
  4. 4. Follow Tenda's documented firmware upgrade procedure, typically involving uploading the firmware file through the device's web administration interface.
  5. 5. After upgrading, verify the httpd component version or confirm the vulnerability is resolved.
  6. 6. If no newer firmware is available, consider contacting Tenda support directly for security patches.
Caveat Review Tenda's firmware release notes for any configuration or feature changes between versions

Generated from the published advisory — verify against the referenced sources before acting.

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

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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