Skip to content
Security

Tenda AC19, CVE-2026-123966: a new CVE scored 10

·7 min read

The bottom line

Check whether you run Tenda AC19. If you do, read the vendor's page for the fixed version and update. Nothing public says yet that anyone is using this flaw.
Cover page of Tenda AC19, CVE-2026-123966: a new CVE scored 10Free analysis report · 9 pagesTenda AC19, CVE-2026-123966: a new CVE scored 10The same note as a document you can keep or forward: what the sources say, who is affected, and what to do first.Download the analysis report →

At a glance

FactDetail
ProductTenda AC19 (CVE-2026-123966)
SeverityCritical: 10 (CVSS 4.0)
StatusA new CVE record, published by VulDB on 7 November 2026. Not on CISA's list of exploited vulnerabilities when we read it on 8 November 2026, which means nothing public says yet that anyone is using it.
Fixed inNo source we read names a fixed version
Who looks firstAnyone managing a Tenda AC19 router on firmware 16.03.10.07. The record states the attack is possible remotely; the degree of exposure depends on who can reach the router's web interface.

Does this apply to you?

Answer in order. Stop at the first no.
QuestionIf noIf yes
Do you run a Tenda AC19 router?Nothing to do for this CVE.Check the firmware version.
Is it on firmware 16.03.10.07?The record does not list your version as affected — monitor for a Tenda update.Check whether the admin interface is reachable from outside your network.
Is the router's web admin interface reachable from outside your local network?Risk is reduced — apply a patch as soon as one is available.Block that access immediately and ask your IT contact about a firmware update.

What it is

The record describes a heap-based buffer overflow in the router's saveParentControlInfo web endpoint. Sending a crafted request with an oversized deviceId value corrupts memory on the device. The record states the attack can be carried out remotely and that a working exploit has been publicly disclosed.

Exposure by situation

These priorities are our judgement from what the sources say about who can use the flaw and how. They are not vendor ratings.

Where you stand, and how soon
Your situationPriorityTimeframe
AC19 on firmware 16.03.10.07, admin interface reachable from the internetMediumBlock external access today
AC19 on firmware 16.03.10.07, admin interface on the LAN onlyMediumThis week — apply patch when available
AC19 present but firmware version not yet confirmedMediumConfirm version today
AC19 running a firmware version other than 16.03.10.07LowMonitor; no action until a fix is confirmed
No Tenda AC19 in the estateNoneNo action needed for this CVE

Things people will get wrong

  • The overflow is in one endpoint, so the rest of the router is unaffected. A heap-based buffer overflow in a web handler can allow code execution across the entire device, not just the endpoint where it occurs.

How we would triage it

This is our judgement.

Step 1: Find the firmware version on each AC19

  • Log in to the router's web admin interface and locate the firmware or system status page, where the installed version is displayed.
  • Confirm whether it reads 16.03.10.07, which is the version the record lists as affected.

Step 2: Restrict access to the admin interface

  • Using your firewall or the router's own access-control settings, ensure the web admin interface is reachable only from trusted hosts on the local network, not from the internet.
  • This reduces the attack surface while you wait for a patched firmware release.

Step 3: Check for a firmware update from Tenda

  • Check Tenda's support pages for a firmware release for the AC19 that addresses this flaw. The record names no fixed version at the time of writing.
  • Do not apply a release unless you can confirm it addresses CVE-2026-123966 or is published after 7 November 2026 and explicitly supersedes 16.03.10.07.

To close it, read the version from the product itself, not from an old inventory, and save the output with the date. If you cannot update today, write down who owns it, the new date, and what limits exposure until then.

The weakness behind it

The record classes this as CWE-122 and CWE-119.

Likely ATT&CK mapping

MITRE ATT&CK is a public catalogue of the steps attackers take, from getting in to causing damage. No source has mapped this flaw to it yet, so the steps below are our prediction from what the record says the flaw allows. They are not MITRE's, the vendor's or CISA's, and an attacker may do other things.

Steps an attacker would likely take with this flaw
The step, in plain wordsStage of an attackWhy we think so
Exploit Public-Facing Application (T1190): Breaking in through a service that faces the internet, such as a web server, VPN or login page.Initial Access: getting inThe flaw is in a web endpoint reachable over the network; exploiting it would likely be the initial access step, as the description names a remotely reachable form handler as the entry point.
Command and Scripting Interpreter (T1059): Running commands or scripts on a machine, such as a shell or PowerShell.Execution: running the attacker's codeA heap-based overflow on an embedded router device would typically lead to arbitrary code execution, likely via the device's built-in command interpreter.
Exploitation of Remote Services (T1210): Exploiting a flaw in a service on another machine to move to it.Lateral Movement: moving to other machinesA compromised perimeter router could be used to reach internal hosts; gaining control of the device would likely enable further movement into the local network.

How to use this: ask your IT provider which control or log would show each step, for example whether sign-in attempts from the internet are recorded. If nobody can answer, that is the gap to close first.

MITRE ATT&CK® is a registered trademark of The MITRE Corporation. Technique names are MITRE's.

The sources, in their words

The CVE record:

A vulnerability was determined in Tenda AC19 16.03.10.07. Affected by this issue is the function saveParentControlInfo of the file /goform/saveParentControlInfo. This manipulation of the argument deviceId causes heap-based buffer overflow. The attack is possible to be carried out remotely. The exploit has been publicly disclosed and may be utilized.

Versions of Tenda AC19 the record lists as affected:

  • 16.03.10.07

The record gives no version ranges. Use the vendor's advisory for the affected versions.

Check your own project

If you build software, you can compare what a project declares with this CVE from a terminal. The tool reads requirements files, package.json, Maven, Gradle, Cargo, CMake and Dockerfile files, runs nothing, and only the CVE id leaves your machine. Naming the CVEs needs no key.

lattice-scan project . --cve CVE-2026-123966

Each row says in-range, outside-range, undetermined or lead, with the file and line. That is evidence about what a manifest declares, not about what runs, and a person decides. The verdicts, the CSV columns and a pipeline recipe are in the guide.

Check the servers you run

The same id can be checked against a host. Run this on the machine itself, not on the laptop that deploys to it: it reads installed packages (dpkg, rpm or apk), snaps, the hardware (maker, model, firmware), the running container images with their operating system and packages, and the kernel version, compares them on the spot, and only the CVE ids leave the machine; the inventory stays on it, in ~/.lattice-scan. Naming the CVEs needs no key. Do it on each server after a deployment, and again when a new entry lands.

lattice-scan --cve CVE-2026-123966

A match is a candidate for a person to confirm, not a finding. A distribution can fix a CVE under an unchanged version number, so a match is a candidate; on Debian-family hosts the report also shows whether the package's own changelog names the CVE. By default it opens the images your containers are running and reads their operating system and package list; a deep scan (--deep, a few minutes) opens every local image and the Python, Node, Java and Ruby packages inside them; for what an image declares, use the project check on its Dockerfile.

Guide: namiq.io/lattice/guides/choose-your-channel. MCP server (io.namiq/lattice in the MCP registry): namiq.io/lattice. Package: pypi.org/project/lattice-scan, or namiq.io/apt.

What we do not know yet

  • Whether authentication is required before the saveParentControlInfo endpoint can be reached — the record does not say.
  • Whether Tenda plans to release a patched firmware for the AC19, and when.
  • Whether the flaw affects other Tenda router models or other firmware versions of the AC19.
  • What level of access a successful exploit provides on the device.
  • Exploitation is not recorded. That is not the same as none.
  • This is a new record: scores, versions and wording can change in the first days, and they are as at 8 November 2026. We have not read the vendor's advisory page and we have not tested it.
  • The sections headed "Does this apply to you?", "What it is", "Exposure by situation", "Things people will get wrong", "Likely ATT&CK mapping" and "How we would triage it" are our interpretation of the sources, not a statement by CISA or the vendor.

Does this touch your business?

A new vulnerability is a question about what you run, who can reach it and what it would cost you. If you want a person to answer it for your own systems, start with your IT setup.

Also worth reading

Start with one piece of work.

Give us one piece of work and read access to one system. We map it and come back with what we found, what we would build and what it would take — before any commitment. You decide using our output, not our pitch.

Talk to us