Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-71985 – Unauthenticated OS Command Injection (RCE) – MSI Radix AXE6600 firmware up to v7815

Be the first to know when new zero-days emerge:

Summary

CVE-2026-71985 is an unauthenticated OS command injection vulnerability in the accesscontrol function of MSI Radix AXE6600 router firmware. A remote, unauthenticated attacker can send crafted input to this function to execute arbitrary commands with root privileges on the device. The flaw is rated CRITICAL, with published CVSS scores of 9.8 (v3.1) and 9.3 (v4.0).

Technical details

  • Root cause: CWE-78 – improper neutralization of special elements used in an OS command; user-supplied input passed to the accesscontrol function is not adequately sanitized before being used in a system command.
  • Trigger conditions: An attacker submits a specially crafted request to the device’s accesscontrol functionality over the network.
  • Attack vector: Network-based, no authentication required, no user interaction required.
  • Impact: Full compromise of the router, including arbitrary command execution and root-level privileges on the underlying operating system.

Affected software

  • MSI Radix AXE6600 (WiFi 6E Tri-Band Gaming Router) — firmware version v781521 and earlier.

Severity

  • CVSS v3.1: 9.8 (Critical) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • CVSS v4.0: 9.3 (Critical) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: No official patched firmware has been confirmed as available at time of publication; check MSI’s support page for the Radix AXE6600 for firmware updates addressing this issue and apply as soon as one is released.
  • If no patch: Disable remote/WAN administration access to the router, restrict management interfaces to trusted internal networks only, place the device behind a firewall or VPN to prevent direct internet exposure, and monitor for unexpected outbound connections or configuration changes on affected devices.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: MSI Router
  • Raw response body: GRAXE66, RadiX AXE6600

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge