CVE-2025-11586
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 determined in Tenda AC7 15.03.06.44. This affects an unknown function of the file /goform/setNotUpgrade. This manipulation of the argument newVersion causes stack-based buffer overflow. The attack is possible to be carried out remotely. The exploit has been publicly disclosed and may be utilized.
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 confidenceA stack-based buffer overflow vulnerability exists in the Tenda AC7 router firmware (v15.03.06.44) within the /goform/setNotUpgrade web interface handler. The newVersion parameter is not properly bounds-checked before being copied to a stack-allocated buffer, allowing an attacker to overwrite return addresses and achieve remote code execution without authentication.
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= 15.03.06.44CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck the router label or access the web interface and look for the model name (AC7) in the device info pageAffected if Device is not a Tenda AC7 router, then not affected by this specific CVE
-
Check the firmware versionAccess the router's web administration page, navigate to System Settings or Firmware Upgrade section, and locate the firmware version displayed. Alternatively, check the downloaded firmware file name or version text if you have the firmware binary.Affected if Firmware version is NOT exactly 15.03.06.44, then not affected by this CVE (only this specific version is listed as affected)
-
Verify web interface accessibilityAttempt to access the router's web interface by entering the router's IP address in a web browser. The default is typically 192.168.0.1 or 192.168.1.1.Affected if Web interface is accessible and responds, confirming the attack surface exists
-
Confirm newVersion parameter handlingSend a crafted HTTP POST request to /goform/setNotUpgrade with an oversized newVersion parameter (e.g., newVersion=AAA... repeated characters) and observe if the request triggers unusual behavior or crashes the web serviceAffected if The router responds without error or crashes to an oversized newVersion value, indicating the vulnerability may be present (this is a confirmatory test and should only be done in authorized testing)
-
Check if remote administration is enabledIn the router web interface, navigate to Advanced Settings or Remote Management and check if remote access from WAN is enabledAffected if Remote administration is enabled, the device is exposed to remote attack vectors for this vulnerability
A user is affected if they have a Tenda AC7 router running firmware version 15.03.06.44 with the web management interface accessible (especially if remote administration is enabled), as this specific version contains the stack-based buffer overflow in the setNotUpgrade handler's newVersion parameter.
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.
dbcve · scopedApply vendor firmware patch when available; otherwise, restrict access to the router's web management interface from untrusted networks or disable remote administration to reduce attack surface.
Latest firmware version available from www.tenda.com.cn for Tenda AC7 (contact vendor for specific version number)
- 1. Identify the current firmware version of the Tenda AC7 router via the web management interface or physical device label
- 2. Access the Tenda official support page at www.tenda.com.cn and navigate to the AC7 product support section
- 3. Download the latest available firmware version for the AC7 from the official Tenda website
- 4. Access the router's web management interface (typically at 192.168.0.1) and navigate to the firmware upgrade section
- 5. Upload and apply the latest firmware version following the on-screen instructions
- 6. After reboot, verify the new firmware version matches the updated release
- 7. As an additional precaution, disable remote web management (WAN access) if not required, limiting attack surface to the local network only
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11586 — 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-2025-11586 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