dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-10119

HIGH · 8.8 CVSS v3.1 Published 2026-05-30
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

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 vulnerability has been detected in TRENDnet TEW-432BRP 3.10B20. Impacted is the function formSetMACFilter of the file /goform/formSetMACFilter. The manipulation of the argument filter_name leads to stack-based buffer overflow. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used. The vendor explains: "This product has been EOL for 15 years (since 2009). As the item has been EOL for such a long time, we are not able to replicate or fix any vulnerabilities." 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 TRENDnet TEW-432BRP router's web interface (function formSetMACFilter). The filter_name parameter passed to /goform/formSetMACFilter is not properly bounds-checked before being copied to a stack buffer, allowing remote attackers to potentially overwrite return addresses and execute arbitrary code. The vulnerability is exploitable remotely without authentication.

MitigationReplace the end-of-life device with a supported router model. If immediate replacement is not feasible, restrict access to the device's web management interface via network segmentation or firewall rules, and disable the MAC filtering feature.

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 the router model
    Check the device label or web interface header to confirm the hardware is a TRENDnet TEW-432BRP router
    Affected if The device is not a TRENDnet TEW-432BRP model
  2. Check firmware version
    Log into the router web interface (usually at 192.168.10.1) and navigate to the firmware or status page to view the installed firmware version, or check the device firmware file if you have local access
    Affected if The firmware version matches 3.10B20
  3. Verify web interface is accessible
    Attempt to access the router web interface over HTTP from both the local network and any external IP if remote management is enabled
    Affected if The web interface responds and accepts authentication
  4. Check if remote management is enabled
    In the router web interface, locate the remote management or web management settings (often under Administration or Advanced) and verify whether remote access from WAN is permitted
    Affected if Remote management is enabled and the web interface is exposed to untrusted networks
  5. Determine if MAC filtering is accessible
    Locate the MAC filtering section in the router web interface (typically under Wireless or Access Control settings) to confirm the formSetMACFilter function exists and is reachable
    Affected if MAC filtering feature is present and accessible in the web interface

You are affected if you are running a TRENDnet TEW-432BRP router with firmware version 3.10B20, the web interface is accessible, and the MAC filtering feature is available, especially if remote management is enabled.

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

Replace the end-of-life device with a supported router model. If immediate replacement is not feasible, restrict access to the device's web management interface via network segmentation or firewall rules, and disable the MAC filtering feature.

Recommended fix Low confidence

Replace with a currently supported TRENDnet router model (contact TRENDnet for current supported product lines)

  1. This vulnerability affects TRENDnet TEW-432BRP 3.10B20, which has been End-of-Life (EOL) since 2009.
  2. The vendor (TRENDnet) has explicitly stated they cannot replicate or fix vulnerabilities in this EOL product.
  3. Replace the affected device with a currently supported TRENDnet router model that receives security updates.
  4. If immediate replacement is not possible, restrict network access to the device's management interface to trusted IP addresses only using firewall rules.
  5. Consider placing the device behind a NAT or in a restricted VLAN to limit exposure to remote attackers.
Caveat Device replacement will require reconfiguration of network settings

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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