dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-15480

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 identified in Trendnet TEW-635BRM up to 1.00.03. This affects the function start_httpd of the file /sbin/rc of the component Web Service. Such manipulation of the argument device_name leads to stack-based buffer overflow. The attack can be executed remotely. The exploit is publicly available and might be used. The vendor explains: "We are unable to confirm if the vulnerability exists. This item has been EOL since 2011. We will make an official announcement of possible vulnerabilities, and recommend users to switch devices." 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 · high confidence

Stack-based buffer overflow in the start_httpd function of the Trendnet TEW-635BRM web service. The vulnerability is triggered via manipulation of the device_name argument in the /sbin/rc script, allowing remote attackers to potentially execute arbitrary code. A public exploit exists and the CVSS score of 8.8 indicates high severity.

MitigationThis device is End-of-Life since 2011 and the vendor will not provide a patch. The recommended remediation is to replace the affected device with a supported model, as no firmware update will be released.

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
    Access the router's web管理界面 or CLI and verify the model number displays as Trendnet TEW-635BRM. This can typically be found in the web interface under 'Status' or 'System' information.
    Affected if The device is not a Trendnet TEW-635BRM model.
  2. Check firmware version
    In the router's web interface, navigate to the Status or System page and locate the firmware version field. Compare the installed version against 1.00.03 using numeric comparison (1.00.03 or lower is affected).
    Affected if The firmware version is 1.00.03 or any version lower than 1.00.03.
  3. Verify web service is enabled
    Check if the web management interface is accessible by attempting to reach the router's IP address on HTTP port 80 or HTTPS port 443 from an authorized network. The vulnerability resides in the start_httpd function in /sbin/rc.
    Affected if The web management interface responds to HTTP/HTTPS requests.
  4. Assess web interface network exposure
    Determine if the web management interface is accessible from untrusted networks (WAN/Internet). Check router firewall settings or NAT configuration. The vulnerability can be exploited remotely if the web interface is exposed.
    Affected if The web management interface is reachable from untrusted or external networks without restriction.

A user is affected if they own a Trendnet TEW-635BRM router running firmware version 1.00.03 or lower, with the web management interface enabled and accessible, especially from untrusted networks.

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

This device is End-of-Life since 2011 and the vendor will not provide a patch. The recommended remediation is to replace the affected device with a supported model, as no firmware update will be released.

Recommended fix High confidence

Replace with a currently supported Trendnet router or alternative vendor device with active security support

  1. This vulnerability affects the Trendnet TEW-635BRM (EOL since 2011) which is no longer supported by the vendor.
  2. The vendor (Trendnet) has explicitly stated they cannot confirm the vulnerability and will not provide patches.
  3. Replace the EOL device with a currently supported router model.
  4. If replacement is not immediately possible, isolate the device behind a firewall or NAT to limit remote attack surface.
  5. Disable remote web management if not required, or restrict access to trusted IP addresses only.
Caveat Device replacement required - no firmware patch will be released for this EOL product

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Review / QA1.0 h
2.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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