CVE-2026-6120
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 detected in Tenda F451 1.0.0.7. Affected is the function fromDhcpListClient of the file /goform/DhcpListClient of the component httpd. The manipulation of the argument page results in stack-based buffer overflow. The attack can be launched remotely. The exploit is now 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 confidenceStack-based buffer overflow in Tenda F451 router httpd component. The fromDhcpListClient function in /goform/DhcpListClient fails to properly validate the 'page' argument length before copying to a fixed-size stack buffer, allowing remote attackers to overwrite stack memory and potentially execute arbitrary code.
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= 1.0.0.7CVSS 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.
-
Identify the router modelAccess the router's web interface or check the device label/marketing materials to confirm it is a Tenda F451 router.Affected if The device is not a Tenda F451 model, then it is not affected by this specific CVE.
-
Check the firmware versionLog into the router web interface and navigate to System Status or Firmware Upgrade page to view the installed firmware version. Alternatively, check via telnet/SSH if enabled: 'cat /proc/version' or 'nvram get firmware_version' if accessible.Affected if The firmware version is exactly 1.0.0.7, then the device is affected. Versions other than 1.0.0.7 are not within the affected range.
-
Verify the httpd service is runningCheck if the httpd web server process is active on the router. This may require telnet/SSH access to run: 'ps | grep httpd' or checking if port 80 or 443 is listening.Affected if If httpd is not running or not listening on any port, the specific vulnerability path is not reachable, reducing risk.
-
Confirm network accessibility of the vulnerable endpointAttempt to access the /goform/DhcpListClient endpoint from an authorized network position using a tool like curl: 'curl http://<router_ip>/goform/DhcpListClient'. Check if the router responds to requests targeting this path.Affected if If the endpoint responds and the device is a Tenda F451 on firmware 1.0.0.7, the vulnerability is present and exploitable.
A Tenda F451 router running firmware version 1.0.0.7 with the httpd service accessible and the /goform/DhcpListClient endpoint exposed indicates the environment is affected by CVE-2026-6120.
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 dataApply vendor firmware patch when available; until then, restrict network access to the router's web interface or disable remote management to reduce attack surface.
- 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-6120 — 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-6120 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