← Back to Feed CACHED · 2026-07-07 10:29:40 · CACHE_KEY CVE-2026-11405
CVE-2026-11405 · CWE-912 · Disclosed 2026-07-06

The web server binary /bin/httpd contains a hidden backdoor authentication mechanism in the login

ASSESSED — NOISGATE V0.5
Vendor
Reassessed
Verdict:
Do you agree?
01 · The Real Story

The router vendor left a spare key under the mat and won't answer the phone to come take it back

CVE-2026-11405 is a hidden authentication backdoor baked into /bin/httpd on five Tenda consumer/SOHO router firmware builds: US_AC6V2.0RTL_V15.03.06.51_multi_T, US_AC5V1.0RTL_V15.03.06.48_multi_TDE01, US_AC10V1.0re_V15.03.06.46_multi_TDE01, US_W15EV1.0br_V15.11.0.5(1068_1567_841)_EN_TDE, and US_FH1201V1.0BR_V1.2.0.14(408)_EN_TD. Inside the login() function at offset 004c88b8, after the normal MD5 password check fails, the binary falls through to GetValue("sys.rzadmin.password") and does a strcmp() against the submitted password. Any match grants role=2 — full admin — and hands back a valid session cookie against the web management UI.

There is no vendor CVSS because CERT/CC could not reach Tenda for coordination — the advisory (VU#213560) shipped uncoordinated on 2026-07-06 with no patch available. In a home use case this would rate around a 7; in an enterprise context where a Tenda unit is fronting a branch office, a lab, or a remote worker VPN concentrator, it's a full gateway takeover with no fix path. That combination — pre-auth admin, no patch, orphaned vendor, network-edge role — pushes this out of the CVSS-arithmetic zone and into 'if you find one, treat it like it's already owned'.

"Vendor-planted backdoor in a network edge device with no patch and no vendor response — HIGH the moment one shows up in your fleet."
02 · The Attack Path

5 steps from start to impact.

STEP 01

Locate a reachable Tenda web UI

Attacker enumerates the affected models. From the WAN side this means Shodan/Censys/FOFA queries for the Tenda login page fingerprint (Server: httpd, favicon hash, HTML title Tenda|W15E|AC10|AC5|AC6|FH1201). From the LAN side, any commodity scanner (Nmap, RustScan) picks it up on TCP/80 or TCP/443. Tooling: shodan search http.favicon.hash:… product:Tenda, nuclei fingerprint templates for Tenda routers.
Conditions required:
  • Attacker can reach the router's HTTP(S) management interface
  • Remote management is enabled on WAN, or attacker already has an internal foothold / adjacent Wi-Fi
Where this breaks in practice:
  • Most enterprises don't run consumer Tenda routers at the perimeter
  • Remote management on WAN is off by default on most Tenda builds
  • The management UI may be bound to LAN only
Detection/coverage: External ASM tools (Bitsight, RiskIQ/Defender EASM, runZero) fingerprint Tenda banners; GreyNoise tags mass Tenda login probes
STEP 02

Submit backdoor credential to the login endpoint

Attacker POSTs to /login/Auth (or model-equivalent) with any username and the backdoor password value. The MD5 path fails, then GetValue("sys.rzadmin.password") returns the vendor-planted string and strcmp() succeeds. A weaponized single-request PoC is trivial — expect curl one-liners and Metasploit / nuclei modules within days. Reference: CERT/CC VU#213560 disassembly at 004c88b8.
Conditions required:
  • Router is running one of the five listed firmware builds
  • sys.rzadmin.password config key is populated (default from factory in reported units)
Where this breaks in practice:
  • Only these five specific builds are documented — other firmwares in the same product line may not carry the same offset
  • If an operator wiped sys.rzadmin.password via NVRAM edit, strcmp against a random secret still fails
Detection/coverage: No public IDS signature yet; login page brute-force alerts won't catch a single successful auth
STEP 03

Receive admin session cookie

The server issues a session token with role=2 (admin). Attacker now controls the same interface a legitimate admin would: WAN config, DHCP, DNS, port forwarding, firmware upload, VPN client/server. This is equivalent to physical access to the router.
Conditions required:
  • Backdoor auth succeeded in step 2
Where this breaks in practice:
  • None — this is the intended (backdoor) flow
Detection/coverage: Router-side syslog if enabled will record an admin login from the attacker IP; almost nobody ships Tenda SOHO syslog to a SIEM
STEP 04

Weaponize the gateway

With admin, attacker rewrites DNS to point clients at an attacker resolver (credential harvest, TLS downgrade), adds port-forwards to expose internal hosts, uploads modified firmware for persistence (botnet enrollment — Mirai/Mozi variants historically pivot on Tenda), or enables the router's OpenVPN/PPTP server to tunnel into the LAN. Tooling: custom firmware images, dnschef, off-the-shelf botnet loaders.
Conditions required:
  • Admin session from step 3
  • Router model supports the abused feature (firmware upload, VPN server, custom DNS)
Where this breaks in practice:
  • Modified firmware may brick the unit and tip off the operator
  • Enterprise DNS clients pinned to internal resolvers or using DoH ignore the router's DNS
Detection/coverage: EDR/DNS telemetry from endpoints behind the router will show anomalous resolvers; NetFlow shows new tunnel egress
STEP 05

Pivot into whatever sits behind the router

If the Tenda unit is a branch-office gateway, a lab-network router, or a remote-worker device, everything behind it is now reachable via port-forwards or the router-hosted VPN. This is a full network-edge compromise: MitM, LAN sweep, lateral movement into corporate assets that trust the branch subnet.
Conditions required:
  • Reachable internal assets behind the router
  • Trust relationship between the branch subnet and corp (site-to-site VPN, flat routing)
Where this breaks in practice:
  • Zero-trust segmentation forces re-authentication at every internal service
  • SASE / SSE tunnels bypass the local router and cut off pivot value
Detection/coverage: SIEM correlation on branch-subnet source IPs hitting unusual internal destinations
03 · Intelligence Metadata

The supporting signals.

In-the-wild exploitationNone publicly reported as of 2026-07-07; not on CISA KEV. Historical pattern for Tenda backdoors is rapid Mirai/Mozi variant adoption within 2–4 weeks.
Proof-of-conceptNo public PoC repo yet. CERT/CC advisory names the exact function offset (004c88b8) and config key (sys.rzadmin.password) — writing a curl one-liner is trivial from the advisory alone.
EPSSNot yet scored (published 2026-07-06). Expect rapid climb into the 90th+ percentile once nuclei/Metasploit modules land.
KEV statusNot listed as of 2026-07-07.
CVSSNo vendor/authority score. noisgate assessment: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H9.8 if WAN-exposed; drops to ~7.5 if LAN-only. Blended: 8.2.
CWECWE-912 Hidden Functionality (a.k.a. backdoor).
Affected firmwareTenda AC6 V15.03.06.51, AC5 V15.03.06.48, AC10 V15.03.06.46, W15E V15.11.0.5(1068_1567_841), FH1201 V1.2.0.14(408) — US regional builds specifically.
Fixed versionNone. CERT/CC states vendor was unreachable for coordination; no patched firmware exists.
Exposure dataShodan historically indexes ~200k–400k Tenda web interfaces globally; the fraction on these specific builds is unknown. Enterprise ASM tools (runZero, Defender EASM) fingerprint the login page reliably.
Disclosure / reporterPublished 2026-07-06 as CERT/CC VU#213560. Reporter is anonymous per acknowledgements.
04 · The Call

noisgate verdict.

Final Verdict
= UNCHANGED to HIGH (8.2/10)

The single most decisive factor is role multiplier + no patch: the affected component is a network edge device, and when one lands in a branch office or remote-worker setup the chain ends in full gateway takeover with no vendor remediation path. The floor set by the network-edge role catalog is HIGH; we do not push to CRITICAL because Tenda's installed base inside enterprise networks is small and the WAN-management exposure population is narrow.

HIGH backdoor exists and is trivially exploitable once reachable
HIGH no patch will arrive on the current disclosure trajectory
MEDIUM prevalence inside typical enterprise fleets
LOW current in-the-wild exploitation volume (too early)

Why this verdict

  • Pre-auth admin, single request — no user interaction, no chained bug, no memory-corruption reliability tax. Once the endpoint is reachable, exploitation is a curl POST.
  • No vendor patch and no vendor contact — this is not a 'patch by X date' problem; it's a rip-and-replace problem. That elevates the mitigation-side severity independent of CVSS math.
  • Role multiplier: network edge appliance — per the noisgate high-value role catalog, a router is a gateway. Chain outcome on a branch-office or remote-worker deployment is DNS hijack, port-forward-driven internal access, and VPN-server abuse for LAN pivot. This sets the floor at HIGH.
  • Friction adjustment down from CRITICAL — Tenda is consumer/SOHO gear rarely present in an enterprise 10k-host fleet; WAN-side management is off by default on most builds; the five listed firmware strings are narrow. That narrows the reachable population enough to sit below CRITICAL but not below HIGH.
  • No KEV, no public PoC yet — keeps this below the 'patch immediately, hours' bar reserved for actively-exploited edge bugs, but the disassembly-in-advisory pattern makes weaponization a matter of days.

Why not higher?

CRITICAL is reserved for vulns where the canonical deployment role of the component is high-value AND the reachable population is broad. Tenda SOHO routers occupy the network-edge role opportunistically inside enterprises (shadow IT, branch offices, home workers) rather than by definition, and WAN-facing admin is not the default posture. Without an active KEV listing or observed campaigns, CRITICAL over-cries.

Why not lower?

MEDIUM would ignore the role multiplier: when one of these devices IS in your environment, the outcome is gateway takeover with no vendor fix — that is not a MEDIUM outcome. The absence of a CVSS baseline and the presence of an intentional vendor backdoor (CWE-912) with no coordination path means treating this as backlog hygiene would be malpractice.

05 · Compensating Control

What to do — in priority order.

  1. Inventory for Tenda hardware across the fleet within 7 days — Run runZero / Defender EASM / Nmap fingerprint sweeps for the Tenda httpd banner and login-page HTML across every corp subnet, branch office, and remote-worker VPN pool. You cannot mitigate what you have not found. Deploy within the 30-day noisgate mitigation window; start day one.
  2. Disable WAN-side (remote) management on any Tenda unit found — In the router UI: System Tools → Remote Web Management → Disable. This removes the internet-reachable attack surface immediately and buys time while you plan replacement. Do within 30 days of inventory hit.
  3. ACL the management interface to a dedicated admin VLAN — On the upstream switch/firewall, restrict TCP/80 and TCP/443 to the router's LAN IP to a single jump-host subnet. Blocks LAN-adjacent attackers (rogue guest Wi-Fi, compromised endpoints) from reaching the backdoor.
  4. Replace with a supported model on a 90-day schedule — Vendor is unreachable; no patch is coming. Any HIGH device without a remediation path must be swapped out. Target UniFi, MikroTik, Meraki, or an enterprise-supported alternative within the 180-day noisgate remediation window — sooner if the unit is WAN-management-exposed.
  5. Ship router syslog to your SIEM and alert on admin logins — Enable System Log → Remote Syslog on the Tenda, point at a rsyslog collector, and alert on any admin login not sourced from your admin VLAN. Detective control until replacement lands.
  6. Force DoH/DoT on endpoints behind Tenda units — Endpoint-enforced encrypted DNS (Cloudflare/Quad9/internal DoH resolver via MDM) neutralizes the router-side DNS-hijack payoff even if the router is owned.
What doesn't work
  • Changing the admin password — the backdoor path reads a SEPARATE config key (sys.rzadmin.password), not the admin password. Rotating the primary credential does nothing.
  • WAF / IPS in front of the router — the router IS the edge. There is nothing 'in front' of it on the WAN side.
  • Enabling HTTPS on the management UI — TLS protects credentials in transit; it does not remove a hardcoded credential accepted by the server.
  • MFA on the router UI — Tenda's login flow does not enforce a second factor after the backdoor strcmp() succeeds; MFA (where even supported) is bypassed by the backdoor branch.
  • Waiting for a vendor patch — CERT/CC could not reach the vendor. This is a rip-and-replace, not a patch-and-hold.
06 · Verification

Crowdsourced verification payload.

Run from an auditor workstation on the same network segment as the router (or with routed reachability to its management IP). Invoke as ./check-cve-2026-11405.sh 192.168.0.1 — no privileges required. Fingerprints the login page against the five known-vulnerable Tenda firmware strings.

noisgate-verify.sh
BASHREAD-ONLYSAFE
#!/usr/bin/env bash
# noisgate check for CVE-2026-11405 — Tenda /bin/httpd hidden backdoor
# Usage: ./check-cve-2026-11405.sh <router-ip-or-host> [port]
# Exit codes: 0 VULNERABLE, 1 PATCHED/NOT-AFFECTED, 2 UNKNOWN
set -u

TARGET="${1:-}"
PORT="${2:-80}"

if [[ -z "$TARGET" ]]; then
  echo "UNKNOWN: usage $0 <router-ip> [port]" >&2
  exit 2
fi

VULN_STRINGS=(
  "V15.03.06.51"                # AC6 V2.0
  "V15.03.06.48"                # AC5 V1.0
  "V15.03.06.46"                # AC10 V1.0
  "V15.11.0.5(1068_1567_841)"   # W15E V1.0
  "V1.2.0.14(408)"              # FH1201 V1.0
)

UA='noisgate-scanner/1.0'
TMP=$(mktemp)
trap 'rm -f "$TMP"' EXIT

# Grab landing page + typical Tenda status endpoints
for path in "/" "/login.html" "/goform/SysStatusRpm" "/system.asp"; do
  curl -sk --max-time 6 -A "$UA" "http://${TARGET}:${PORT}${path}" >> "$TMP" 2>/dev/null || true
done

if ! grep -qiE 'tenda|W15E|AC6|AC5|AC10|FH1201' "$TMP"; then
  echo "UNKNOWN: no Tenda fingerprint at ${TARGET}:${PORT} — target may not be a Tenda device, or UI is not on this port"
  exit 2
fi

for v in "${VULN_STRINGS[@]}"; do
  if grep -qF "$v" "$TMP"; then
    echo "VULNERABLE: Tenda device at ${TARGET} advertises firmware string '$v' — matches CVE-2026-11405 (CERT/CC VU#213560). No vendor patch exists."
    exit 0
  fi
done

echo "PATCHED-OR-NOT-AFFECTED: Tenda device detected but firmware string does not match any of the five known-vulnerable builds. Manually confirm firmware in System Tools -> System Status."
exit 1
07 · Bottom Line

If you remember one thing.

TL;DR
Monday morning: run a fleet-wide Tenda fingerprint sweep (Nmap, runZero, or the verification script) against every corp subnet, branch office, and remote-worker VPN pool — you almost certainly have zero of these in a hardened enterprise, but shadow-IT and branch-office boxes are the whole point of this hunt. For every hit, disable WAN-side remote management the same day and shove the management UI behind an admin-VLAN ACL. Under the noisgate mitigation SLA for HIGH, those compensating controls must be in place within 30 days of inventory. Under the noisgate remediation SLA for HIGH, the physical device must be replaced with a supported vendor (UniFi, MikroTik, Meraki) within 180 days — there is no patch coming from Tenda. If any Tenda unit turns up with WAN admin exposed OR shows an admin login you cannot attribute, treat the segment behind it as compromised and act on that assumption within hours.

Sources

  1. CERT/CC VU#213560 — Tenda firmware hidden authentication backdoor
  2. The Hacker News — CERT/CC Warns of Hidden Admin Backdoor in Tenda Router Firmware
  3. ThreatINT CVE-2026-11405 record
  4. Cryptika — Tenda Authentication Backdoor Grants Attackers Full Administrative Access
  5. MITRE CWE-912 — Hidden Functionality
  6. CISA Known Exploited Vulnerabilities Catalog
  7. FIRST EPSS
  8. Tenda official support / firmware downloads
Peer Review

What defenders are saying.

Submit a review attribution: handle + country only
0 flags selected · stored anonymously
Validation Results

Crowdsourced verification outputs.

Results submitted by users who ran the verification payload against their environment.