On this page (7 sections)
A critical vulnerability, tracked as CVE-2026-123966, has been published for the Tenda AC19 router running firmware 16.03.10.07. The flaw is a heap-based buffer overflow in a function named saveParentControlInfo, and the record says it can be attacked remotely and that the exploit has been publicly disclosed.
If you run a Tenda AC19 at an office, a shop, a branch site or a client location, this is worth checking today. The sources we have are thin: there is no vendor advisory and no patched version listed, so much of the advice below is general exposure reduction rather than a confirmed fix.
What was reported
The GitHub Advisory Database entry and the matching NVD record were both published on November 7, 2026. They describe a flaw in the function saveParentControlInfo of the file /goform/saveParentControlInfo. Manipulating the deviceId argument causes a heap-based buffer overflow.
The NVD page repeats the same text as the GitHub entry, so these are not two independent confirmations. The references also point to a public write-up on GitHub and to VulDB entries. We have not independently verified those, and we do not reproduce any exploit details here.
Technical details in plain terms
A heap-based buffer overflow happens when a program copies more data into a memory buffer than it was sized to hold, and the buffer lives on the heap (the dynamic memory area). The extra data overwrites neighboring memory. Depending on the device, that can crash a service or, in worse cases, let an attacker change how the program behaves.
According to the record, the input that reaches the faulty code is the deviceId argument of the saveParentControlInfo function. From the function name and the /goform/ path, it looks like a web-based form handler related to parental controls, but that is our inference; the research does not describe what the handler does or how it is exposed. The CVSS v4 metrics in the advisory list the attack vector as Network, complexity as Low, with no privileges and no user interaction required, and high impact on confidentiality, integrity and availability.
Those metrics are what drive the 9.3 score. They do not tell us what an attacker actually achieves on a real device. The research does not say whether code execution is demonstrated, or whether the flaw is reachable from the internet side by default or only from the local network. It also does not say whether any router setting changes that reachability.
Who is realistically exposed
The research names only the Tenda AC19 on firmware 16.03.10.07, so that is the group to check first. Beyond that, the following are reasonable places to look, with the caveat that the research does not confirm how the flaw is reached:
- Sites where a Tenda AC19 is the main router or gateway, such as small offices, shops, clinics and home offices.
- Networks where untrusted users or devices share the LAN, since the CVSS attack vector is listed as Network and we do not know which network paths reach the affected function.
- Devices whose web administration might be reachable from the internet side. The research does not say whether this matters here, but an exposed management page is a common risk for routers in general.
- Agencies and IT providers who installed these routers for clients and may not have an inventory of them.
A compromised edge router is a bigger problem than the device itself. It sits in the path of network traffic, so in general it can affect DNS settings, routing and access to internal systems, including servers that host your websites if they are on the same network. The research does not report any such compromise for this CVE.
How to check your exposure
- Identify whether you have an AC19. The model name is printed on the label on the device and usually shown in its admin page.
- Log in to the router admin page from inside your network and read the firmware version on the system or status page. Compare it with 16.03.10.07.
- Look in the remote management or web administration settings and note whether access from the WAN or internet side is enabled.
- From a network outside yours (for example a phone on mobile data), check whether your public IP address answers on the router's web ports. If it does, a management page is exposed to the internet.
Menu names vary between firmware builds, so we do not give exact click paths. If you manage websites behind the router, you can also run a read-only check of your public address and certificate with the free SSL checker, though that does not test the router itself.
What to do now
No patched version is named in the research, and it does not say which settings, if any, block the vulnerable function. The steps below are general exposure reduction for a router with an unpatched critical flaw. They may lower your risk, but we cannot confirm that they block this specific path. Watch for a firmware update from the vendor.
- Inventory every Tenda AC19 you manage and record its firmware version.
- Disable remote (WAN-side) administration on each one, as a general precaution.
- Restrict access to the admin interface to a trusted wired host or a dedicated management VLAN where the router supports it.
- Do not assume that leaving parental control unconfigured removes the exposure; the research does not say whether that blocks the vulnerable function.
- Check the Tenda website and the device's firmware page for a newer release, and install it once one is published for the AC19.
- Change the router admin password to a unique, long value and review the DNS, port forwarding and DHCP settings for entries you do not recognize.
- Put a firewall or a second router in front of any server that must stay reachable, so the AC19 is not the only barrier.
- Plan a replacement if the vendor does not publish a fix, especially for devices that protect business traffic.
Detection and monitoring
Because there is no patch yet, watch the router and what depends on it. Warning signs to look for:
- Unexpected router reboots or admin page crashes, which can follow a failed overflow attempt.
- Changed DNS servers, new port forwarding rules or new admin accounts that nobody on your team created.
- Unfamiliar outbound connections from the router, if your upstream firewall or ISP gives you that visibility.
- Sudden redirects, certificate warnings or slow loading on your sites from the affected location.
If you host a website behind this kind of router, uptime, certificate and DNS monitoring can alert you to downtime, a changed certificate or altered DNS records, which are things a router compromise can cause. It will not tell you whether the router itself is vulnerable. For general background, see our guide on what to do if a website is hacked.
If you suspect the router was already taken over, factory reset it, reconfigure it from scratch with new credentials, and rotate any passwords that crossed the network, such as VPN, email and admin logins.
What is still unknown
- Whether Tenda has acknowledged the issue or plans a fix. The research includes no vendor advisory.
- Which firmware versions other than 16.03.10.07 are affected.
- Whether attacks are happening in the wild. The record says only that the exploit is public and may be used. The research shows no CISA Known Exploited Vulnerabilities entry for this CVE, but that is an absence of data, not a statement from CISA.
- Whether the flaw can be triggered without logging in. The CVSS metrics say no privileges are required, but they come from the scoring in the record, not from our own testing.
- Which network interfaces expose the affected function, and whether any router setting blocks it.
We will treat this as an evolving story. A public exploit tends to increase scanning of exposed devices, so reducing exposure now is sensible even without confirmed attacks.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
