dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-10122

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 vulnerability has been found in TRENDnet TEW-432BRP 3.10B20. This affects the function formSetProtocolFilter of the file /goform/formSetProtocolFilter. Such manipulation of the argument protocol_name leads to stack-based buffer overflow. The attack may be performed from remote. The exploit has been disclosed to the public 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 formSetProtocolFilter function allows remote attackers to overflow the protocol_name argument, potentially executing arbitrary code. The vulnerability is exploitable over the network with low attack complexity and no authentication required, resulting in HIGH (8.8) CVSS score.

MitigationSince the device is End-of-Life (EOL since 2009) with no vendor support, replace the affected router with a currently supported model. If replacement is not immediately feasible, isolate the device on a restricted network segment to limit exposure.

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 device model
    Access the router's web administration interface and check the status page or system info section for the exact model number (TEW-432BRP). Alternatively, check the device label or packaging.
    Affected if The device is a TRENDnet TEW-432BRP router
  2. Verify the web management interface is accessible
    Attempt to access the router's web interface at its default IP address (typically 192.168.10.1) via HTTP. Confirm the interface loads and accepts authentication.
    Affected if The web interface is exposed and reachable on the network
  3. Confirm the Protocol Filter feature exists
    Navigate through the router's web interface to locate the Protocol Filter or similar firewall/filtering settings. This is where the vulnerable formSetProtocolFilter function would be invoked.
    Affected if A Protocol Filter or firewall rule configuration feature is present and accessible
  4. Check for firmware version information
    In the router's web interface, look for a System or Administration section that displays the firmware version. Compare this against any known version numbers for the TEW-432BRP.
    Affected if The firmware version cannot be determined or falls within an unpatched release range

The device is affected if it is a TRENDnet TEW-432BRP router with an accessible web management interface where the Protocol Filter feature can be accessed, as the buffer overflow resides in the formSetProtocolFilter function handling that feature.

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 device is End-of-Life (EOL since 2009) with no vendor support, replace the affected router with a currently supported model. If replacement is not immediately feasible, isolate the device on a restricted network segment to limit exposure.

Recommended fix High confidence
  1. This is a legacy EOL device (since 2009) with no vendor support or patches available.
  2. Replace the affected TRENDnet TEW-432BRP with a currently supported router from the vendor or an alternative manufacturer.
  3. If immediate replacement is not possible, implement network segmentation to isolate the affected device on a restricted VLAN with minimal network permissions.
  4. Disable remote administration interfaces if not strictly necessary, limiting attack surface to local network access only.
  5. Monitor the network for any suspicious traffic patterns targeting the device.

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
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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