Stack-based Buffer Overflow in Tenda HG7/HG9/HG10 formDOMAINBLK
CVE-2026-11499 is a remotely exploitable stack-based buffer overflow affecting Tenda HG7, HG9, and HG10 devices running firmware version 300001138_en_xpon. The flaw is present in the formDOMAINBLK function exposed via the /boaform/formDOMAINBLK endpoint. According to the available information, improper handling of the blkDomain argument allows an attacker to supply crafted input that overflows a stack buffer. Successful exploitation could corrupt stack memory and alter control flow, potentially resulting in arbitrary code execution or process crash on the affected device.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a minimal two-file proof-of-concept for CVE-2026-11499 affecting Tenda HG7/HG9/HG10 routers. The code consists of a single Python script, CVE-2026-11499.py, plus a README describing the vulnerability at a high level. The exploit is not part of a larger framework and is focused solely on sending a crafted HTTP POST request to the router web interface. The PoC’s core capability is denial-of-service testing via a suspected stack-based buffer overflow in the /boaform/formDOMAINBLK handler. It constructs an oversized blkDomain form value using repeated 'A' characters and submits it with additional fields (submit-url=/domainblk.asp and page=domainblk) and a Referer header pointing to /domainblk.asp. The script interprets HTTP timeout or connection failure as evidence that the router or web service crashed. An optional incremental mode increases payload size from 100 to 950 bytes in 50-byte steps to help identify an approximate crash threshold. There is no authentication bypass, shellcode delivery, reverse shell, RCE chain, persistence, or post-exploitation logic. Although the README mentions potential RCE conceptually, the actual code only demonstrates crash-oriented behavior and should be classified as a PoC DoS exploit rather than a weaponized RCE exploit. The repository structure is straightforward: one executable Python entry point and one documentation file. The main fingerprintable targets are the router management paths /boaform/formDOMAINBLK and /domainblk.asp, along with the blkDomain parameter used as the overflow vector.
Recent activity
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.