dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-10120

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 was detected in TRENDnet TEW-432BRP 3.10B20. The affected element is the function formSetFirewallRule of the file /goform/formSetFirewallRule. The manipulation of the argument firewall_name results in stack-based buffer overflow. The attack can be executed remotely. The exploit is now 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 firmware 3.10B20 within the formSetFirewallRule function, where the firewall_name parameter can be overflown to potentially achieve remote code execution or denial of service.

MitigationSince the device is End-of-Life and unpatchable, replace with a supported router model or implement network isolation/segmentation with strict firewall rules 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 router model
    Access the router's web interface or check the device label/metadata to confirm the model is TRENDnet TEW-432BRP
    Affected if The device is not a TEW-432BRP model - then this specific CVE does not apply
  2. Check the firmware version
    In the router web interface, navigate to the Status or System section to view the firmware version. It should display as 3.10B20
    Affected if The firmware version is 3.10B20 exactly - this is the affected version
  3. Verify the web management interface is accessible
    Attempt to access the router's web interface at its IP address (typically 192.168.10.1) via HTTP or HTTPS. Confirm the interface responds to requests
    Affected if The management interface is accessible (especially from wide-area networks) - this is required for the attack vector
  4. Confirm the formSetFirewallRule endpoint exists
    Check if the router's firewall configuration page is reachable. The vulnerability exists in the formSetFirewallRule function used by the firewall settings interface
    Affected if The firewall management features are present and accessible through the web interface

You are affected if you have a TRENDnet TEW-432BRP router running firmware version 3.10B20 with the web management interface accessible, as the formSetFirewallRule endpoint contains the buffer overflow in the firewall_name parameter handling

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 and unpatchable, replace with a supported router model or implement network isolation/segmentation with strict firewall rules to limit exposure.

Recommended fix High confidence
  1. Implement network segmentation to isolate the affected device from untrusted networks
  2. Place the TRENDnet TEW-432BRP behind a properly configured firewall or NAT gateway to limit remote attack surface
  3. If the device's firewall functionality is not critically needed, disable remote management interfaces
  4. Monitor network traffic for indicators of exploitation attempts against the formSetFirewallRule endpoint
  5. Replace the EOL device with a currently supported router that receives security updates

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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