dbcve.org
InjectionWeakness · CWE-74

CVE-2026-15481

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 security flaw has been discovered in Trendnet TEW-635BRM up to 1.00.03. This vulnerability affects the function ipoa_test of the file /sbin/rc of the component IPoA WAN Connection Setup. Performing a manipulation of the argument ipoa_ipaddr results in command injection. The attack is possible to be carried out remotely. The exploit has been released to the public and may be used for attacks. 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

Command injection vulnerability in Trendnet TEW-635BRM routers (firmware up to 1.00.03) allows remote attackers to execute arbitrary commands via the ipoa_ipaddr parameter in the ipoa_test function within the /sbin/rc script used for IPoA WAN Connection Setup.

MitigationDevice is End-of-Life since 2011 with no vendor patch available; replace affected devices with supported hardware and implement network segmentation to isolate legacy devices if continued operation is required.

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
    Identify the router model by checking the device label, web interface, or SNMP inventory. Look for 'TEW-635BRM' marking.
    Affected if The device is not a Trendnet TEW-635BRM router (different models are not affected by this specific CVE).
  2. Check firmware version
    Access the router web interface (typically at 192.168.1.1) and navigate to the Firmware Upgrade or Status page to view the installed firmware version. Alternatively, check via command line if SSH/Telnet access is available.
    Affected if Firmware version is 1.00.03 or any earlier version (the vulnerability exists in all versions up to and including 1.00.03).
  3. Verify IPoA WAN configuration
    In the router web interface, examine WAN Connection settings or IPoA configuration options. Look for any active IPoA (IP over ATM) WAN connection profiles.
    Affected if IPoA WAN Connection Setup is enabled or configured - the ipoa_test function in /sbin/rc is only invoked when this feature is used.
  4. Inspect /sbin/rc script
    If shell access is available, examine the /sbin/rc file and search for the 'ipoa_test' function. Look for unsafe use of the 'ipoa_ipaddr' parameter in system commands.
    Affected if The /sbin/rc script contains the ipoa_test function and processes the ipoa_ipaddr parameter without proper sanitization (vulnerable code pattern present).

You are affected if you own a Trendnet TEW-635BRM router running firmware version 1.00.03 or lower AND have IPoA WAN Connection Setup enabled or have accessed the vulnerable ipoa_test functionality.

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

Device is End-of-Life since 2011 with no vendor patch available; replace affected devices with supported hardware and implement network segmentation to isolate legacy devices if continued operation is required.

Recommended fix High confidence
  1. This vulnerability affects the Trendnet TEW-635BRM router, which has been End of Life (EOL) since 2011.
  2. The vendor (Trendnet) has explicitly stated they cannot confirm this vulnerability and will not provide a fix.
  3. The vendor recommends users to switch to a newer, supported device.
  4. Replace the affected device with a currently supported router from Trendnet or another vendor.
  5. If replacement is not immediately possible, isolate the device from untrusted networks using firewall rules or network segmentation.
Caveat Device replacement required - the affected model is end-of-life since 2011 with no vendor support

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing2.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,540
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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