Security readout for executives and security teams
Plain-English summary
Tenda G0 devices running firmware reported through 20260625 contain a remotely reachable memory-corruption flaw in the web management service. An authenticated attacker could trigger a stack overflow through static-route configuration. Public exploit material increases urgency, although the supplied sources do not establish active exploitation or confirm a vendor fix.
Executive priority
Prioritize immediate inventory and exposure reduction for affected Tenda G0 devices. Internet-accessible management interfaces warrant emergency handling because exploit material is public and potential impact is severe. For isolated devices, schedule rapid remediation while monitoring vendor guidance. Do not claim compromise solely from version presence.
Technical view
CVE-2026-19791 affects addStaticRoute in /goform/module within the Tenda G0 httpd management interface. Manipulating staticRouteNet can cause a stack-based buffer overflow (CWE-119/CWE-121). The CVSS v2 vector scores 9.0 and indicates network access with authentication. Exact execution outcomes are not established by the supplied evidence.
Likely exposure
Exposure is highest where a Tenda G0 management interface is reachable from untrusted networks and firmware is 20260625 or an earlier affected release. Authentication is indicated as required. The supplied sources do not clarify default exposure, affected deployment counts, or whether other firmware versions are safe.
Exploitation context
Proof-of-concept exploit material is publicly available, making testing and adaptation easier for attackers. The CVE is not listed as KEV in the supplied bundle, and no cited evidence confirms exploitation in the wild. Treat public management-interface exposure and compromised administrator credentials as significant risk multipliers.
Researcher notes
The record attributes the overflow to staticRouteNet in addStaticRoute and classifies it as CWE-119/CWE-121. CVSS v2 reports authentication required and complete confidentiality, integrity, and availability impacts. Public proof-of-concept availability is documented, but successful code execution, active exploitation, patch availability, and precise affected-version boundaries remain insufficiently established.
Mitigation direction
- Identify Tenda G0 devices and record their exact firmware versions.
- Remove web management access from the public internet and restrict it to trusted administrators.
- Require network-level access controls for the management interface.
- Review Tenda guidance for patched firmware or vendor-approved mitigation; none is identified in the supplied sources.
- Rotate management credentials if unauthorized access is suspected.
Validation and detection
- Confirm whether each device runs firmware 20260625 or an earlier reported release.
- Verify the management interface is unreachable from untrusted networks.
- Review access logs for unexpected requests to /goform/module and static-route configuration changes.
- Check device stability, configuration history, and administrator accounts for unexplained changes.
- Confirm remediation against current Tenda guidance without sending exploit traffic.
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-19791 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.
SSVC decision data
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.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- VDB-389759 | Tenda G0 httpd web management interface module addStaticRoute stack-based overflowCVE reference, VulDB · vdb-entry, technical-description
- VDB-389759 | CTI Indicators (IOB, IOC, IOA)CVE reference, VulDB · signature, permissions-required
- CVE-2026-19791 | CVE Analysis and ReportCVE reference, VulDB · third-party-advisory
- Submit #868927 | Tenda G0 Tenda G0 Buffer OverflowCVE reference, VulDB · third-party-advisory
- https://github.com/lipenghai/iot_bug/blob/main/Tenda/G0/2.mdCVE reference, VulDB · exploit
- 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.