dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-15484

HIGH · 8.8 CVSS v3.1 Published 2026-07-12
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 5 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 TRENDnet TEW-821DAP 1.12B01. The affected element is the function sub_41EC14 of the file /goform/tools_nslookup of the component ssi. The manipulation results in buffer overflow. It is possible to launch the attack remotely. The vendor explains: "We are unable to confirm the existence of the vulnerabilities for (...) TEW-821DAP (v1.0R) as these items have been EOL. " This vulnerability only affects products that are no longer supported by the maintainer.

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 confidence

A buffer overflow vulnerability exists in the tools_nslookup function (sub_41EC14) within the ssi component of TRENDnet TEW-821DAP firmware version 1.12B01. The vulnerability is present in the /goform/tools_nslookup web interface handler and can be exploited remotely, potentially allowing arbitrary code execution.

MitigationSince the affected product is End-of-Life and will not receive vendor patches, recommended mitigations include replacing the device with a currently supported model and implementing network-level controls such as restricting access to the device's management interface from untrusted networks or VLANs.

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. Confirm device model is TEW-821DAP
    Access the device web interface or check the device label/marketing to identify the exact model number
    Affected if Device is not a TRENDnet TEW-821DAP unit
  2. Check firmware version is 1.12B01
    Log into the web interface and navigate to System > Firmware or Status page to view the installed firmware version; compare against 1.12B01
    Affected if Firmware version is exactly 1.12B01
  3. Verify the web interface is enabled and accessible
    Attempt to access the device's HTTP/HTTPS web interface on the configured IP address
    Affected if Web interface is accessible on the network
  4. Confirm the nslookup tool exists in the web interface
    Navigate to Tools or Network section in the web interface and locate the nslookup/diagnostics function (typically under Tools > Network Tools or similar)
    Affected if The nslookup or network diagnostics feature is present and accessible

User is affected if they are running a TRENDnet TEW-821DAP with firmware version 1.12B01 and the web interface with the nslookup tool is accessible on their network.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the affected product is End-of-Life and will not receive vendor patches, recommended mitigations include replacing the device with a currently supported model and implementing network-level controls such as restricting access to the device's management interface from untrusted networks or VLANs.

Recommended fix High confidence
  1. Since the affected product (TRENDnet TEW-821DAP) is End of Life (EOL) and the vendor has explicitly stated they cannot confirm or provide fixes for this vulnerability, no vendor-supplied fix is available.
  2. If the device is still in production use, consider replacing it with a currently supported device from TRENDnet or another vendor.
  3. If replacement is not immediately feasible, restrict network access to the device's web management interface (port 80/443) to trusted IP addresses only to reduce the remote attack surface.
  4. Monitor the device for any signs of compromise since no patch will be released.
Caveat No upgrade path available as product is EOL

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15484 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-15484 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