CVE-2026-11522
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 W20E 15.11.0.6. This vulnerability affects the function formSetPortMirror of the file /goform/setPortMirror. Performing a manipulation of the argument portMirrorMirroredPorts results in stack-based buffer overflow. The attack can be initiated 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 confidenceA stack-based buffer overflow vulnerability exists in the Tenda W20E router firmware version 15.11.0.6. The vulnerability is in the formSetPortMirror function within /goform/setPortMirror, where the portMirrorMirroredPorts parameter is copied to a fixed-size stack buffer without proper bounds checking. An attacker can send a crafted HTTP request with an oversized portMirrorMirroredPorts value to overwrite stack memory and potentially execute arbitrary code remotely.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelAccess the router web interface or check the device label to confirm the model is Tenda W20EAffected if Device is not a Tenda W20E router
-
Check firmware versionNavigate to the router administration page, typically under System Settings or Firmware Upgrade, and note the firmware version displayed. Alternatively, check via CLI if available using 'cat /proc/version' or 'ver' command.Affected if Firmware version is 15.11.0.6
-
Verify port mirroring configurationAccess the router web UI and navigate to the Port Mirroring or Traffic Monitor settings page (usually under Advanced or Network settings). Check if port mirroring is enabled and note any configured mirrored ports.Affected if Port mirroring feature is enabled with any port configuration
-
Confirm endpoint accessibilityAttempt to access the URL '/goform/setPortMirror' on the router's web interface. This is the vulnerable endpoint. If it responds (even with an error), the endpoint is exposed.Affected if The /goform/setPortMirror endpoint is reachable from the network
A user is affected if they own a Tenda W20E router running firmware version 15.11.0.6 with the port mirroring feature enabled and the web management interface accessible to untrusted networks.
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 any vendor-supplied firmware update when available. If no patch exists, disable the port mirroring feature if unnecessary, restrict network access to the device's management interface, and monitor for exploitation attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11522 — 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-11522 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