Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-13516

HIGH · 8.8 CVSS v3.1 Published 2026-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 7 weeks old

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
A vulnerability was detected in Tenda JD12L 16.03.53.23. The affected element is the function fromSetWifiGusetBasic of the file /goform/WifiGuestSet. Performing a manipulation of the argument shareSpeed results in stack-based buffer overflow. The attack may 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 confidence

A stack-based buffer overflow vulnerability exists in Tenda JD12L router firmware 16.03.53.23 within the fromSetWifiGusetBasic function in /goform/WifiGuestSet. The shareSpeed parameter is not properly bounds-checked before use, allowing an attacker to overflow the stack buffer by supplying an overly long value.

MitigationApply vendor firmware update if available; otherwise, disable WiFi guest network functionality or restrict management interface access to trusted networks to reduce attack surface.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify router model and firmware version
    Access the router admin web interface or check the device label/metadata to confirm the model is Tenda JD12L and note the installed firmware version. Compare against 16.03.53.23.
    Affected if The router is a Tenda JD12L with firmware version 16.03.53.23 or earlier.
  2. Verify WiFi guest network feature is accessible
    Log into the router admin panel and navigate to the WiFi or wireless settings section. Look for a guest network or guest WiFi configuration option.
    Affected if The WiFi guest network feature is enabled or configurable on the router.
  3. Confirm vulnerable endpoint exists
    Attempt to access or ping the /goform/WifiGuestSet endpoint on the router's web interface (e.g., http://router-ip/goform/WifiGuestSet). This is the web handler for the vulnerable function.
    Affected if The endpoint responds, indicating the vulnerable function is present in the firmware.
  4. Check if shareSpeed parameter is accepted
    Submit a request to /goform/WifiGuestSet with a normal shareSpeed value (as part of the guest network configuration). Observe whether the parameter is processed without validation errors.
    Affected if The shareSpeed parameter is accepted and processed by the guest network settings function.

A user is affected if they are running Tenda JD12L router firmware 16.03.53.23 or earlier with the WiFi guest network feature accessible and the /goform/WifiGuestSet endpoint responsive to shareSpeed parameter input.

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 if available; otherwise, disable WiFi guest network functionality or restrict management interface access to trusted networks to reduce attack surface.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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