← Back to Feed CACHED · 2026-08-10 00:14:56 · CACHE_KEY CVE-2026-71993
CVE-2026-71993 · CWE-78 · Disclosed 2026-08-09

MSI Radix AXE6600 router firmware version v781521 contains a command injection vulnerability in the openvpn…

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

A smoking hole in a toy nobody brought to the office

CVE-2026-71993 is an unauthenticated OS command injection in the OpenVPN configuration handler of the MSI Radix AXE6600 consumer Wi-Fi 6E gaming router, firmware version v781521 and earlier. Unsanitized input in the macfilter / openvpn web interface function is passed directly to a shell command, giving an attacker full root-level execution on the router's embedded Linux OS. This is one of at least eight nearly identical CWE-78 command injection CVEs (CVE-2026-71984 through CVE-2026-71993) disclosed simultaneously by researcher Jincheng Wang against the same firmware image, affecting functions like urlfilter, accesscontrol, dmz, alg, TelnetSSH, and macfilter.

The vendor CVSS of 9.8 CRITICAL is technically accurate *for the vulnerability mechanics* — it is indeed unauthenticated, network-reachable, and yields root. But for an enterprise security team, the severity is wildly overstated because the affected product has effectively zero enterprise footprint. The MSI Radix AXE6600 is a $220 consumer gaming router sold on Amazon and Walmart. It is not a managed enterprise edge appliance (Fortinet, Palo Alto, Cisco), not rack-mountable, has no centralized management, and appears in zero enterprise procurement catalogs. Unless your asset inventory specifically shows this SKU, this CVE is noise.

"Consumer gaming router bug - almost certainly not in your 10k-host fleet."
02 · The Attack Path

3 steps from start to impact.

STEP 01

Reach the router admin interface

The attacker must reach the AXE6600’s web management interface, which by default listens only on the LAN-side subnet (typically 192.168.x.1:80/443). Remote management is disabled by default on consumer MSI routers. An attacker on the same LAN segment or with remote admin enabled can proceed.
Conditions required:
  • Network path to the router’s web management interface
  • Remote management enabled OR attacker on the same LAN
Where this breaks in practice:
  • Default config exposes admin UI only on the LAN side
  • Enterprise networks do not deploy consumer gaming routers as managed infrastructure
  • No Shodan/Censys/GreyNoise signature data exists for this product in meaningful volume
STEP 02

Send crafted OpenVPN configuration request

The attacker sends an HTTP request to the OpenVPN or macfilter endpoint with OS command metacharacters (e.g., ; id or $(whoami)) injected into a parameter. No authentication token or session cookie is required. The router’s CGI handler passes the value directly to a shell invocation.
Conditions required:
  • Reachability to the web interface (Step 1)
Where this breaks in practice:
  • No public PoC exploit code has been identified as of 2026-08-10
  • The batch of 8+ CVEs suggests the researcher used straightforward parameter fuzzing, so reproduction is trivial for a skilled attacker
Detection/coverage: No IDS/IPS signatures exist for this product. Generic command-injection WAF rules would not apply because enterprise WAFs do not sit in front of consumer router admin panels.
STEP 03

Achieve root shell on the router

The injected command executes as root (consumer routers typically run all services as root). The attacker now has full control of the router: can intercept/modify traffic, pivot to LAN hosts, exfiltrate DNS queries, or brick the device.
Conditions required:
  • Successful command injection (Step 2)
Where this breaks in practice:
  • Blast radius is limited to a single consumer router and the LAN segment behind it
  • No lateral movement to Active Directory, enterprise services, or managed endpoints follows from owning a home gaming router
03 · Intelligence Metadata

The supporting signals.

In-the-wild exploitationNone observed. No reports from any threat intel vendor, no CISA KEV listing, no GreyNoise/Shadowserver activity.
Proof of conceptNo public PoC as of 2026-08-10. The batch disclosure by Jincheng Wang included advisory-level detail only. Reproduction is trivial given the CWE-78 class.
EPSS score0.0135 (approximately 80th percentile) — low predicted exploitation probability.
KEV statusNot listed. No CISA KEV entry.
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H — 9.8 CRITICAL. Also scored CVSS v4.0 9.3 CRITICAL.
Affected versionsMSI Radix AXE6600 firmware v781521 and earlier. Single consumer SKU (GRAXE66).
Fixed versionUnknown. MSI support portal referenced but no specific patched firmware version number confirmed publicly.
Exposure dataNegligible enterprise exposure. No meaningful Shodan/Censys/GreyNoise footprint. Product is a consumer gaming router sold via Amazon, Walmart, and MSI direct. Not present in enterprise procurement catalogs.
Disclosure date2026-08-09 (reserved 2026-08-08). Part of a batch of 8+ CVEs against the same firmware.
ResearcherJincheng Wang, assigned via VulnCheck CNA.
04 · The Call

noisgate verdict.

Final Verdict
DOWNGRADED to LOW (2.5/10)

The single most decisive factor is near-zero enterprise installed base: the MSI Radix AXE6600 is a consumer gaming router with no meaningful enterprise deployment, so the vulnerability’s severe technical impact (unauthenticated root RCE) has no fleet-scale relevance. The blast radius of a successful exploit is confined to a single home router and its LAN — it does not touch domain controllers, managed endpoints, or enterprise data tiers.

HIGH Vulnerability mechanics and severity of the technical flaw
HIGH Assessment that enterprise fleet impact is negligible
MEDIUM Absence of public PoC (could appear any day given trivial reproduction)

Why this verdict

  • Installed base is consumer-only: The MSI Radix AXE6600 is a $220 Wi-Fi 6E gaming router. It is not sold through enterprise channels, has no central management platform, and does not appear in any enterprise asset management or CMDB data at scale. Probability of this SKU existing in a 10,000-host enterprise fleet is near zero.
  • Role multiplier: not applicable. This is NOT an enterprise network edge appliance (Fortinet, Palo, Cisco, F5). It occupies role (a) — consumer/home-office device. Even if a remote worker uses one at home, compromising it does not grant access to the corporate network beyond what the VPN tunnel already encrypts end-to-end. Blast radius: single device + home LAN. No high-value role applies.
  • Admin interface is LAN-only by default: Even for the tiny population that owns this router, the attack surface requires LAN adjacency or explicitly enabled remote management, narrowing reachable targets further.
  • No exploitation evidence or PoC: EPSS is 0.0135, no KEV listing, no observed campaigns, no public exploit code. The batch of 8 similar CVEs against one firmware suggests a researcher audit, not active adversary interest.

Why not higher?

The vulnerability is technically severe (unauthenticated RCE to root), so if this were a widely-deployed enterprise edge appliance like FortiGate or PAN-OS, it would be CRITICAL with no debate. The *only* reason for the aggressive downgrade is that the affected product is a consumer gaming router with effectively zero enterprise presence. If your CMDB shows AXE6600 units, re-evaluate to HIGH.

Why not lower?

Despite negligible enterprise relevance, the flaw is real, unauthenticated, trivially exploitable, and yields root. A blanket IGNORE would be inappropriate for any organization that *does* have this hardware, and the PoC-less state could change overnight given how simple CWE-78 reproduction is in consumer routers.

05 · Compensating Control

What to do — in priority order.

  1. Confirm the AXE6600 is not in your asset inventory — Run a CMDB/NAC query for MSI networking hardware or the GRAXE66 model string. If zero results, document the finding and close the ticket. This should take minutes, not days.
  2. If found: disable remote management immediately — On any discovered unit, ensure the WAN-side remote management interface is disabled (it should be off by default). This eliminates the network-adjacent attack vector from the internet.
  3. If found: segment the device off the enterprise network — Consumer routers should never be inline on an enterprise network. Place any discovered units behind a managed firewall or replace them with supported enterprise hardware.
  4. If found: apply firmware update when MSI releases one — Monitor the MSI support portal for a patched firmware. Given the LOW noisgate severity, no mitigation SLA applies — treat as backlog hygiene.
What doesn't work
  • IDS/IPS signatures — no vendor has released signatures for this product, and enterprise IDS does not inspect traffic to consumer router admin panels.
  • WAF rules — enterprise WAFs protect web applications, not router admin interfaces on LAN segments.
  • EDR/XDR — endpoint agents do not run on consumer router firmware; they cannot detect or prevent exploitation of the router itself.
06 · Verification

Crowdsourced verification payload.

Run this on any Linux/macOS auditor workstation with network access to your CMDB or asset management API export. No special privileges required. Example: bash check_axe6600.sh /path/to/asset_export.csv

noisgate-verify.sh
BASHREAD-ONLYSAFE
#!/usr/bin/env bash
# noisgate CVE-2026-71993 checker
# Searches an asset inventory CSV export for MSI Radix AXE6600 devices.
# Usage: bash check_axe6600.sh <asset_csv_file>
# Exit codes: 0 = PATCHED/not present, 1 = VULNERABLE (devices found), 2 = UNKNOWN

set -euo pipefail

if [ $# -lt 1 ]; then
  echo "Usage: $0 <asset_csv_file>"
  echo "UNKNOWN - no asset file provided"
  exit 2
fi

ASSET_FILE="$1"

if [ ! -f "$ASSET_FILE" ]; then
  echo "UNKNOWN - file not found: $ASSET_FILE"
  exit 2
fi

# Search for MSI Radix AXE6600 or GRAXE66 model identifiers
MATCHES=$(grep -iE '(AXE6600|GRAXE66|radix.*6600|MSI.*radix)' "$ASSET_FILE" 2>/dev/null || true)

if [ -z "$MATCHES" ]; then
  echo "PATCHED - No MSI Radix AXE6600 devices found in asset inventory."
  echo "CVE-2026-71993 is not applicable to this environment."
  exit 0
else
  COUNT=$(echo "$MATCHES" | wc -l | tr -d ' ')
  echo "VULNERABLE - Found $COUNT potential MSI Radix AXE6600 device(s):"
  echo "$MATCHES"
  echo ""
  echo "Action: Verify these devices, disable remote management, and isolate from enterprise network."
  exit 1
fi
07 · Bottom Line

If you remember one thing.

TL;DR
This CVE is almost certainly not your problem. The MSI Radix AXE6600 is a consumer gaming router that does not belong in enterprise networks. Step one Monday morning: run a quick CMDB/NAC query for the AXE6600 or GRAXE66 model string. If you get zero hits, close the ticket and move on — per the noisgate remediation SLA for LOW findings, there is no mitigation SLA and no remediation deadline; treat as backlog hygiene and document the rationale. If you *do* find units (e.g., a branch office or executive home setup), isolate them from the corporate network and replace with managed enterprise hardware. Do not burn patching cycles on this when you have real CRITICAL and HIGH items in your queue.

Sources

  1. THREATINT CVE-2026-71993 Entry
  2. TheHackerWire – CVE-2026-71993 Advisory
  3. TheHackerWire – MSI Radix AXE6600 Command Injection Overview
  4. OffSeq Threat Radar – CVE-2026-71993
  5. MSI Official Product Page – RadiX AXE6600
  6. Dong Knows Tech – MSI RadiX AXE6600 Review
  7. TheHackerWire – TelnetSSH Command Injection (Related CVEs)
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.