Ac7 FirmwareOperating system · Tenda

CVE-2026-51844

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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
Tenda AC7 v15.03.06.44 contains a stack buffer overflow vulnerability in the /goform/AdvSetMacMtuWan interface via the cloneType parameter.

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 buffer overflow vulnerability exists in the Tenda AC7 router firmware v15.03.06.44 within the /goform/AdvSetMacMtuWan web interface. The cloneType parameter fails to properly validate input length before copying data to a stack-allocated buffer, potentially allowing an unauthenticated attacker to achieve remote code execution with elevated privileges.

MitigationApply vendor firmware updates when available; alternatively, disable or restrict access to the affected web interface and implement input length validation on the cloneType parameter.

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
Ac7 FirmwareOperating system
Affected:= 15.03.06.44

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 device model
    Check if the target device is a Tenda AC7 router by accessing the router's web interface or checking the device label/documentation
    Affected if Device is a Tenda AC7 router
  2. Check firmware version
    Access the router's web interface (typically at 192.168.0.1) and navigate to System Settings or Firmware Upgrade to view the installed version, or use firmware extraction methods if you have a firmware image
    Affected if Firmware version is exactly 15.03.06.44
  3. Verify vulnerable endpoint exists
    Attempt to access the URL /goform/AdvSetMacMtuWan on the router's web interface (port 80 or 443)
    Affected if The endpoint responds (returns any HTTP response, even an error page)
  4. Confirm cloneType parameter handling
    Send a crafted HTTP POST request to /goform/AdvSetMacMtuWan with an unusually long string in the cloneType parameter (e.g., 500+ characters) and observe the response
    Affected if The device accepts the request without rejecting it due to input length validation

If the device is a Tenda AC7 running firmware version 15.03.06.44 and the /goform/AdvSetMacMtuWan web interface is accessible, the environment is affected by this vulnerability.

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

Apply vendor firmware updates when available; alternatively, disable or restrict access to the affected web interface and implement input length validation on the cloneType parameter.

Fix this in Ac7 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-51844 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