Somebody left the admin door open with a doormat that says 'just walk in' — but the door is inside the house
CVE-2026-40854 is an authentication bypass in WNC-manufactured T-Mobile 5G Box IDU home internet gateways running firmware prior to 1.1.0.651412. The portal.cgi admin interface validates session cookies by checking whether a matching filename exists under /tmp/login_user/. An attacker on the adjacent network can set the sessionid cookie to . or .. — entries that always exist in any UNIX directory — and walk straight into the admin panel with no credentials. When chained with CVE-2026-40855 (authenticated OS command injection in the same portal.cgi ping function), this becomes unauthenticated root-shell on the gateway. All firmware versions prior to 1.1.0.651412 are affected.
The CVSS 4.0 base score of 8.7 (AV:A) already reflects the adjacent-network limitation, but for enterprise defenders managing corporate fleets the real-world severity is lower. This is a consumer/SOHO 5G home internet gateway — not an enterprise network edge appliance, domain controller, or identity provider. The device is distributed by T-Mobile to residential broadband subscribers (primarily in European markets via WNC/Wistron NeWeb). Its admin interface is only reachable from the local WiFi/LAN segment; it is not exposed to the internet. Unless your organization deploys these specific WNC-branded T-Mobile gateways in branch offices or kiosks — which is uncommon — the blast radius to your enterprise is negligible. The CVSS 8.7 is technically accurate for a home user on the same WiFi, but overstates the risk for a typical enterprise patch queue.
4 steps from start to impact.
Attacker joins the local network
- Adjacent network access (WiFi PSK or wired LAN)
- Attacker must already be on the local network — this eliminates all remote/internet-based attack paths
- WiFi PSK is required unless the network is open or attacker compromises another device first
Forge session cookie with directory traversal
portal.cgi with the sessionid cookie set to . or ... The CGI script checks whether /tmp/login_user/<sessionid> exists — since . and .. are implicit directory entries, the check passes. No brute-forcing, no timing attacks, no tooling beyond curl.- HTTP access to the gateway admin panel (typically 192.168.x.1)
- Trivially exploitable — a single curl command suffices
- No public PoC repo yet, but the technique is self-evident from the advisory
Gain admin panel access
- Successful session forgery from step 2
- Impact is limited to the single gateway and its connected clients
Chain to root shell via CVE-2026-40855
ping_ip, ping_size, ping_times POST parameters in portal.cgi). Commands execute as root on the underlying Linux system. The attacker now owns the gateway's operating system — can install persistent implants, intercept all traffic, or pivot to other LAN devices.- Admin session from step 3
- CVE-2026-40855 present (same firmware versions affected)
- Full root on a consumer gateway — serious for the home user, but limited enterprise value
- No lateral movement to enterprise assets unless VPN/ZTA is absent
The supporting signals.
| In-the-Wild Exploitation | No evidence. Not listed on CISA KEV. No campaigns or threat actor mentions as of 2026-09-17. |
|---|---|
| Proof-of-Concept | No public PoC repository found. However, exploitation is trivially reproducible from the advisory text alone — set sessionid cookie to . via curl. |
| EPSS Score | Not yet scored. CVE was disclosed 2026-09-16; EPSS data typically populates within 7–14 days. |
| KEV Status | Not listed as of 2026-09-17. |
| CVSS Vector | CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N — Base 8.7. Adjacent network (AV:A) is the critical limiter; everything else is worst-case. |
| Affected Versions | All WNC T-Mobile 5G Box IDU firmware prior to 1.1.0.651412. |
| Fixed Version | Firmware 1.1.0.651412 — delivered via T-Mobile OTA update channel. |
| Exposure Data | No Shodan/Censys/GreyNoise hits expected — admin interface is LAN-only, not internet-exposed. The WNC 5G Box IDU is a consumer/SOHO product distributed primarily in European T-Mobile markets. |
| Disclosure Date | 2026-09-16 via CERT Polska coordinated disclosure. |
| Researchers | Patryk Bogdan and Adam Borczyk, coordinated through CERT Polska. |
| Related CVEs | Part of a 6-CVE batch: CVE-2026-40854 through CVE-2026-40857, plus CVE-2026-58146 and CVE-2026-58147. CVE-2026-58146 (unauthenticated command injection via cli_cookie) is the most severe sibling — does not even require the auth bypass. |
noisgate verdict.
The single most decisive factor is the adjacent-network-only attack vector (AV:A) on a consumer/SOHO device with near-zero enterprise deployment share — this CVE cannot be reached from the internet and the affected hardware is not enterprise infrastructure. The trivial exploit complexity and chain to root prevent a LOW rating, but the blast radius is confined to a single home network segment with no path to enterprise domain or fleet compromise.
Why this verdict
- Adjacent-network requirement (AV:A) eliminates remote attack surface. The admin panel is only reachable from the local WiFi/LAN segment. Internet-based attackers cannot reach it. This is the single largest friction factor and removes the vulnerability from any internet-facing risk calculus.
- Consumer/SOHO device with negligible enterprise footprint. The WNC T-Mobile 5G Box IDU is a residential broadband gateway. Enterprise networks do not deploy these as managed infrastructure. The population of affected devices in a typical 10,000-host enterprise fleet is effectively zero.
- Trivial exploitation preserves MEDIUM floor. The auth bypass requires only setting a cookie to
.— no tooling, no race condition, no memory corruption. Combined with CVE-2026-40855, this yields unauthenticated root in two HTTP requests. This mechanical simplicity prevents a LOW rating. - Role multiplier: consumer gateway, not enterprise edge. While this device IS a network perimeter for its home network, it is not an enterprise network edge appliance (F5, Palo Alto, FortiGate). Fewer than 0.1% of enterprise-managed device inventories would include this hardware. The high-value-role floor does not apply because the component is not canonically an enterprise infrastructure device. Compromise yields root on a single home gateway — blast radius is host-level, not domain/fleet/supply-chain.
Why not higher?
A HIGH or CRITICAL rating would require either internet-facing exposure, active exploitation, or deployment in an enterprise-critical role. This CVE has none of those. The adjacent-network vector means an attacker must already have local network access, which for a home gateway implies physical proximity or a separate initial compromise. The device class (consumer 5G gateway) is outside the enterprise high-value-role catalog, so the blast-radius floor does not elevate the verdict.
Why not lower?
A LOW rating would understate the risk because the exploit is *trivially* simple — a single cookie value — and chains directly to root shell via a sibling CVE in the same firmware. For organizations that DO have these devices (e.g., in kiosk, pop-up retail, or temporary branch deployments using T-Mobile 5G Home Internet), the chain is devastating. The mechanical ease of exploitation and the root-level impact on the device itself anchor the floor at MEDIUM.
What to do — in priority order.
- Change the default WiFi PSK to a strong, unique passphrase — The primary attack prerequisite is adjacent-network access. A strong WiFi passphrase prevents casual attackers from joining the network. This is the single most effective compensating control for AV:A vulnerabilities on consumer gateways. No mitigation SLA applies at MEDIUM — go straight to the 365-day remediation window.
- Enable automatic firmware updates on the gateway — T-Mobile delivers firmware OTA. Ensure the device is configured to accept automatic updates so it receives version 1.1.0.651412 without manual intervention. Most consumer gateways have this enabled by default.
- Segment the gateway from enterprise assets — If using a T-Mobile 5G Box IDU for any business purpose, ensure enterprise endpoints connect through a VPN or ZTNA overlay — never trust the gateway's LAN as a security boundary.
- Monitor for CVE-2026-58146 (unauthenticated RCE sibling) — CVE-2026-58146 in the same firmware batch is unauthenticated command injection via
cli_cookie— it does not even need the auth bypass. The same firmware update fixes both. Prioritize awareness of the full 6-CVE batch.
- WAF / IPS at the enterprise perimeter — the vulnerable admin interface is on the device's LAN side, not traversing any enterprise security stack. Perimeter controls cannot inspect or block this traffic.
- Enterprise vulnerability scanners (Qualys, Tenable, Rapid7) — these scanners do not have plugins for consumer T-Mobile gateway firmware. The devices are unmanaged from an enterprise perspective.
- Network ACLs on the gateway itself — the admin panel cannot be restricted to specific source IPs on most consumer gateway firmware; there is no granular access control beyond WiFi authentication.
Crowdsourced verification payload.
Run this on any Linux/macOS machine connected to the same LAN as the T-Mobile 5G Box IDU gateway. Usage: bash check_cve_2026_40854.sh 192.168.12.1 (replace with your gateway IP). No special privileges required — it just sends an HTTP request.
#!/usr/bin/env bash
# check_cve_2026_40854.sh — Test for CVE-2026-40854 auth bypass
# Usage: bash check_cve_2026_40854.sh <gateway_ip>
# Exit codes: 1=VULNERABLE, 0=PATCHED, 2=UNKNOWN
set -euo pipefail
GW_IP="${1:-192.168.12.1}"
URL="http://${GW_IP}/cgi-bin/portal.cgi"
TIMEOUT=5
echo "[*] Testing CVE-2026-40854 against ${GW_IP}"
echo "[*] Sending request with sessionid=. to portal.cgi"
HTTP_CODE=$(curl -s -o /tmp/cve_2026_40854_resp.txt -w '%{http_code}' \
--connect-timeout "${TIMEOUT}" \
--max-time "${TIMEOUT}" \
-b "sessionid=." \
"${URL}" 2>/dev/null || echo "000")
if [ "${HTTP_CODE}" = "000" ]; then
echo "[!] UNKNOWN — could not connect to ${GW_IP}. Is this a WNC T-Mobile 5G Box IDU?"
rm -f /tmp/cve_2026_40854_resp.txt
exit 2
fi
# Check if the response contains admin panel content
# (authenticated pages typically include config/settings elements)
if grep -qi -e 'logout' -e 'admin' -e 'settings' -e 'configuration' -e 'ping_ip' /tmp/cve_2026_40854_resp.txt 2>/dev/null; then
echo "[!] VULNERABLE — authentication bypassed with sessionid=. (HTTP ${HTTP_CODE})"
echo "[!] Firmware is prior to 1.1.0.651412. Update immediately."
rm -f /tmp/cve_2026_40854_resp.txt
exit 1
elif [ "${HTTP_CODE}" = "200" ]; then
# 200 but no admin content — might be login page (patched)
if grep -qi -e 'login' -e 'password' -e 'sign in' /tmp/cve_2026_40854_resp.txt 2>/dev/null; then
echo "[+] PATCHED — received login page, session forgery rejected."
rm -f /tmp/cve_2026_40854_resp.txt
exit 0
else
echo "[?] UNKNOWN — HTTP 200 but unclear response. Manual review needed."
rm -f /tmp/cve_2026_40854_resp.txt
exit 2
fi
elif [ "${HTTP_CODE}" = "302" ] || [ "${HTTP_CODE}" = "401" ] || [ "${HTTP_CODE}" = "403" ]; then
echo "[+] PATCHED — gateway rejected forged session (HTTP ${HTTP_CODE})."
rm -f /tmp/cve_2026_40854_resp.txt
exit 0
else
echo "[?] UNKNOWN — unexpected HTTP ${HTTP_CODE}. Manual review needed."
rm -f /tmp/cve_2026_40854_resp.txt
exit 2
fiIf you remember one thing.
Sources
What defenders are saying.
Crowdsourced verification outputs.
Results submitted by users who ran the verification payload against their environment.