CVE-2026-51380
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 · uneditedBuffer Overflow vulnerability in Tenda AC10 v3 (firmware V03.03.16.09) allows attackers to cause a permanent Denial of Service (DoS) or potentially execute remote code via the /cgi-bin/UploadCfg endpoint
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 · moderate confidenceA buffer overflow vulnerability exists in the /cgi-bin/UploadCfg endpoint of Tenda AC10 v3 routers running firmware V03.03.16.09. The endpoint handles configuration file uploads without proper bounds checking, allowing attackers to overflow the buffer and potentially achieve remote code execution or cause a permanent denial of service.
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
- 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 router modelAccess the router admin interface or check the device label to confirm the model is Tenda AC10 v3Affected if The device is a Tenda AC10 v3 router
-
Check the installed firmware versionLog into the router admin interface and navigate to System Settings or Administration to view the firmware version; alternatively, check via telnet/SSH if enabledAffected if The firmware version is V03.03.16.09
-
Verify if the /cgi-bin/UploadCfg endpoint is accessibleAttempt to access http://[router-ip]/cgi-bin/UploadCfg or check if the CGI binary exists on the device filesystem via telnet/SSHAffected if The endpoint responds or the CGI script is present on the device
-
Confirm if remote administration is enabledCheck the router admin interface under Remote Management or Access Control settings to see if remote HTTP/HTTPS admin access is enabledAffected if Remote administration is enabled and the router is accessible from the WAN interface
You are affected if you have a Tenda AC10 v3 router running firmware V03.03.16.09 with the /cgi-bin/UploadCfg endpoint accessible, especially if remote administration is enabled.
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 the latest firmware update from Tenda if available; if no update exists, restrict administrative access to the /cgi-bin/UploadCfg endpoint via firewall rules or disable remote administration entirely.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2026-51380 — 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-51380 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