Security readout for executives and security teams
Plain-English summary
CVE-2026-10189 is a critical flaw in Tenda W12 firmware 3.0.0.7(4763). A remotely reachable authenticated attacker could trigger a memory corruption issue in the device web service, risking full compromise of the appliance. Public exploit material is cited, but active exploitation is not confirmed.
Executive priority
Treat this as urgent for any exposed or remotely administered Tenda W12 device. Prioritize inventory and isolation first, because the bundle cites public exploit availability and does not provide a confirmed vendor patch.
Technical view
VulDB describes a stack-based buffer overflow in /bin/httpd, function cgiSysTimeInfoSet, caused by manipulation of the sec argument. The CVSS v2 vector is 9.0 with network access, low complexity, single authentication, and complete confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to organizations running Tenda W12 devices on firmware 3.0.0.7(4763), especially where the web management interface is reachable by untrusted networks. The source bundle does not identify other affected versions or products.
Exploitation context
The vulnerability is remotely triggerable and public exploit material is referenced. The CVSS vector indicates authentication is required. CISA KEV status is false in the bundle, and no cited source confirms active exploitation in the wild.
Researcher notes
Evidence comes primarily from CVE/VulDB records. The vulnerable function, binary, parameter, affected firmware, CWE mapping, and CVSS vector are stated. Patch status, vendor acknowledgement, exploit reliability, and live exploitation are not established in the provided sources.
Mitigation direction
- Check Tenda guidance for firmware updates or official mitigation instructions.
- Remove internet exposure for W12 management interfaces.
- Restrict administrative access to trusted management networks only.
- Change exposed administrative credentials if interface exposure is found.
- Replace or isolate affected devices if no vendor fix is available.
Validation and detection
- Inventory Tenda W12 devices and record firmware versions.
- Confirm whether any device runs 3.0.0.7(4763).
- Check whether web management is reachable from untrusted networks.
- Review administrative logs for unexpected time-setting activity.
- Track CVE, VulDB, and Tenda pages for updated remediation guidance.
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-10189 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-367470 | Tenda W12 httpd cgiSysTimeInfoSet stack-based overflowCVE reference, VulDB · vdb-entry, technical-description
- VDB-367470 | CTI Indicators (IOB, IOC, IOA)CVE reference, VulDB · signature, permissions-required
- CVE-2026-10189 | CVE Analysis and ReportCVE reference, VulDB · third-party-advisory
- Submit #820021 | Tenda W12 V3.0.0.7(4763) stackCVE reference, VulDB · third-party-advisory
- https://www.tenda.com.cn/CVE reference, VulDB · product
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.