A vulnerability was found in Tenda AC1206 15.03.06.23_multi_TD01. This affects the function set_device_name of the file /goform/SetOnlineDevName of the component httpd web management interface. The manipulation of the argument devName results in stack-based buffer overflow. The attack may be launched remotely. The exploit has been made public and could be used.
Security readout for executives and security teams
Plain-English summary
A flaw in one Tenda AC1206 firmware version allows a remote user with management access to trigger a memory overflow through the device-name function. The supplied CVSS assessment indicates possible complete compromise of confidentiality, integrity, and availability, but the public evidence does not confirm successful real-world attacks.
Executive priority
Treat confirmed affected devices as an urgent remediation priority, especially when management is remotely reachable. Reduce exposure immediately and obtain current vendor guidance. Replacement should be considered if no supported correction is available, but the supplied sources do not name a patch.
Technical view
CVE-2026-19788 is a stack-based buffer overflow in set_device_name, reached through /goform/SetOnlineDevName in the httpd management interface. Supplying an unsafe devName value can corrupt stack memory. The CVSS 2.0 vector scores 9.0 and indicates network access, low complexity, and single authentication.
Likely exposure
Confirmed scope is Tenda AC1206 firmware 15.03.06.23_multi_TD01. Risk is highest where the web management interface is reachable from untrusted networks or accessible with compromised credentials. The bundle does not establish whether other firmware versions or models are affected.
Exploitation context
A public proof of concept is referenced, so attempted exploitation is plausible. However, the CVE is not listed as KEV in the supplied bundle, and no cited evidence establishes active exploitation in the wild. Authentication appears required according to the CVSS vector.
Researcher notes
The evidence identifies the vulnerable endpoint, function, parameter, and stack-overflow class. It does not establish the precise overwrite conditions, reliable code execution, affected-version range beyond the named build, or observed attacks. One submission title references AC12 while the CVE scope names AC1206; validate device identity carefully.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
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.
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.
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.
4CVSS vectors
6Timeline events
1ADP providers
7Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
4 official scores
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-119 · source CWE mapping
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 represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.