Ac7 FirmwareOperating system · Tenda

CVE-2026-51846

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
In Tenda AC7 v15.03.06.44, the wanSpeed parameter of the route /goform/AdvSetMacMtuWan has a stack buffer overflow vulnerability that can lead to remote arbitrary code execution.

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 buffer overflow in the wanSpeed parameter of the /goform/AdvSetMacMtuWan endpoint in Tenda AC7 firmware v15.03.06.44 allows attackers to overwrite stack memory and achieve remote arbitrary code execution.

MitigationApply vendor firmware update when available; until then, restrict access to the device's web management interface to trusted networks or disable remote administration.

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. Confirm device model is Tenda AC7
    Access the router web interface or check device labeling. The AC7 is a Tenda WiFi router with model number clearly marked on the device.
    Affected if Device is not a Tenda AC7 router, then not affected by this specific CVE.
  2. Check firmware version is 15.03.06.44
    Log into the router web management interface and navigate to System Settings or Firmware version information page. The version number is typically displayed under 'Firmware Version' or 'System Version'. Alternatively, some Tenda routers expose version via the /goform/getSysInfo endpoint.
    Affected if Firmware version is exactly 15.03.06.44 - this is the only affected version for this CVE.
  3. Verify web management interface is accessible
    Attempt to access the router web interface on the default IP (commonly 192.168.0.1 or 192.168.1.1). The vulnerable endpoint is /goform/AdvSetMacMtuWan.
    Affected if Web interface is not accessible from your location (either locally or remotely), but note that if the interface IS accessible and the version matches, the device is vulnerable.
  4. Identify if the AdvSetMacMtuWan endpoint exists
    Send an HTTP GET or POST request to http://[router-ip]/goform/AdvSetMacMtuWan. A valid response (even an error) indicates the endpoint exists.
    Affected if The endpoint responds (indicating the vulnerable web form handler is present), combined with version 15.03.06.44, confirms the device is affected.

Device is affected only if it is a Tenda AC7 router running firmware version exactly 15.03.06.44 and the web management interface with the AdvSetMacMtuWan endpoint is accessible.

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 update when available; until then, restrict access to the device's web management interface to trusted networks or disable remote administration.

Fix this in Ac7 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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