Security readout for executives and security teams
Plain-English summary
This is a critical flaw in an obsolete TRENDnet TEW-432BRP router firmware. A remote authenticated user could trigger a memory corruption condition in domain-filter settings. The vendor says the product has been end-of-life since 2009 and cannot be fixed, so continued use creates unmanaged risk.
Executive priority
Treat this as an urgent legacy-asset removal issue, not a routine patch cycle. There is no vendor fix in the provided sources, public exploit material exists, and unsupported edge devices can create high business risk if reachable.
Technical view
CVE-2026-10123 is a stack-based buffer overflow in formSetDomainFilter on TRENDnet TEW-432BRP 3.10B20. Manipulation of domain-filter arguments can cause overflow. The CVSS v2 score is 9.0 with network access, low complexity, and single authentication required. Public proof-of-concept material is referenced.
Likely exposure
Exposure is limited to TRENDnet TEW-432BRP devices running 3.10B20, especially where administrative access is reachable from untrusted networks. The product is long unsupported, so organizations may only find it in legacy small-office, lab, or unmanaged edge-network environments.
Exploitation context
Sources state the attack can be initiated remotely and that public exploit material exists. CISA KEV status is false in the provided bundle, so there is no sourced evidence here of active exploitation in the wild.
Researcher notes
Evidence is strongest for affected product, vulnerable function, vulnerability class, CVSS score, EOL status, and public proof-of-concept availability. The bundle does not provide verified active exploitation, detailed exploit reliability, or an official patch path.
Mitigation direction
- Inventory for TRENDnet TEW-432BRP devices and confirm firmware versions.
- Retire and replace affected devices with supported network hardware.
- Remove administrative access from the internet and untrusted networks.
- Restrict management access to trusted administrators only.
- Check TRENDnet or VulDB guidance for any updated vendor direction.
Validation and detection
- Review asset inventories for TRENDnet TEW-432BRP 3.10B20.
- Inspect network scans for exposed router administration interfaces.
- Check configuration records for domain-filter functionality use.
- Review logs for suspicious access to /goform/formSetDomainFilter.
- Confirm replacement or isolation status for each discovered device.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-119: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-10123 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:S/C:C/I:C/A:C/E:POC/RL:ND/RC:UR
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
4 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
AV:N/AC:L/Au:S/C:C/I:C/A:C/E:POC/RL:ND/RC:UR810VulDBCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:R2.85.9VulDBCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:R2.85.9VulDBCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P——VulDBVulnerability scoring details
Base CVSS 4.0 score
8.7HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:R
Base CVSS 3.0 score
8.8HighVector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:R
Base CVSS 2.0 score
9CriticalVector: AV:N/AC:L/Au:S/C:C/I:C/A:C/E:POC/RL:ND/RC:UR
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineVulDB
Advisory disclosed
- Source timelineVulDB
VulDB entry created
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineVulDB
VulDB entry last update
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- VDB-367300 | TRENDnet TEW-432BRP formSetDomainFilter stack-based overflowCVE reference, VulDB · vdb-entry, technical-description
- VDB-367300 | CTI Indicators (IOB, IOC, IOA)CVE reference, VulDB · signature, permissions-required
- Submit #814767 | TRENDnet TEW-432BRP 3.10B20 Stack-based Buffer OverflowCVE reference, VulDB · third-party-advisory
- https://github.com/wudipjq/my_vuln/blob/main/TRENDnet/vuln_10/10.mdCVE reference, VulDB · exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Restriction of Operations within the Bounds of a Memory Buffer
Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.