dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-10121

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 flaw has been found in TRENDnet TEW-432BRP 3.10B20. The impacted element is the function formSetUrlFilter of the file /goform/formSetUrlFilter. This manipulation of the argument keyword_list/keyword causes stack-based buffer overflow. The attack is possible to be carried out remotely. The exploit has been published 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 firmware 3.10B20 allows remote attackers to execute arbitrary code via the keyword_list/keyword parameter in the /goform/formSetUrlFilter endpoint. The formSetUrlFilter function fails to properly bounds-check user-supplied input before copying it to a fixed-size stack buffer.

MitigationThis vulnerability has no patch as the device is End-of-Life (EOL since 2009). Recommended remediation involves replacing the EOL device with a currently-supported model or implementing compensating controls such as network isolation/firewalling to restrict access to the vulnerable service.

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 device model
    Access the router web interface or check device label/metadata to confirm the model is TRENDnet TEW-432BRP
    Affected if Device model is TRENDnet TEW-432BRP
  2. Verify web interface is accessible
    Attempt to access the router's web interface via HTTP/HTTPS on the local network (typically at the default gateway IP)
    Affected if Web interface responds and is reachable on the network
  3. Confirm URL filtering feature exists
    Navigate to the URL filtering or content filtering settings page in the router web interface and check if the keyword_list or keyword parameter field is present
    Affected if URL filtering feature with keyword_list/keyword parameter is available in the web interface
  4. Check network exposure
    Determine if the router web interface is accessible from outside the local network (WAN side) or if the device is directly internet-facing
    Affected if Router web interface is accessible from untrusted networks (WAN/Internet)

You are affected if you operate a TRENDnet TEW-432BRP router with its web interface and URL filtering feature exposed on the network, especially if accessible 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 vulnerability has no patch as the device is End-of-Life (EOL since 2009). Recommended remediation involves replacing the EOL device with a currently-supported model or implementing compensating controls such as network isolation/firewalling to restrict access to the vulnerable service.

Recommended fix Low confidence
  1. This vulnerability affects TRENDnet TEW-432BRP firmware version 3.10B20, which has been End-of-Life since 2009.
  2. The vendor (TRENDnet) has explicitly stated they cannot replicate or fix any vulnerabilities in this product due to its EOL status.
  3. There is no patched firmware version available from the vendor for this product.
  4. Consider replacing the affected device with a currently supported model from TRENDnet or another vendor.
  5. If replacement is not immediately possible, place the device behind a properly configured firewall with minimal external exposure to reduce attack surface.

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-10121 — 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-10121 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