CVE-2026-71984
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMSI Radix AXE6600 router firmware version v781521 contains a command injection vulnerability in the urlfilter function that allows remote attackers to execute arbitrary commands on the affected device. Attackers can exploit the urlfilter function to inject malicious commands and obtain root privileges on the underlying system.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisUser input reaches a shell or system command without being fully separated from the command itself, so an attacker can append their own instructions. Because these run with the application's privileges, it often means full control of the host. The lasting fix is to avoid the shell entirely — call APIs directly and pass arguments as data, never as concatenated strings.
General guidance for the os command injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataThere is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $8,900. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-71984 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesThis is a command injection vulnerability in the urlfilter function of the Radix AXE6600 router firmware. The function interfaces with kernel packet filtering (iptables), and the vulnerability arises from unsanitized input being passed to a shell invocation. This is the same pattern that has produced dozens of router CVEs over the past decade — the fix quality is what matters, not just the CVE existence. When assessing this vulnerability in the firmware, your priority is determining whether the patch refactors the invocation pattern or merely adds a blacklist check. Pull the commit diff: if the fix introduces input sanitization (parameterized execution, allowlist validation, or replacement of system() with exec-family functions), this is a genuine remediation. If the fix adds a regex filter on the urlfilter parameter, the vulnerability is patched but the underlying architecture remains vulnerable — the next feature requiring kernel interaction will likely reproduce the same pattern. Check the firmware SDK context. Determine whether the development environment provides safe wrappers for system calls that the developer didn't use, or whether no such tooling exists. If safe wrappers were available but unused, this is an organizational security culture failure. If the toolchain offers no safe alternative to shell invocation, this vulnerability is structural to the firmware development process and will recur. The blast radius extends beyond the AXE6600. If the urlfilter component shares code ancestry with other Radix products — and the discussion indicates this is likely — a perfect fix in one product line doesn't propagate automatically. Audit the other product firmware for the same urlfilter implementation. The CVE scores severity but not exposure: the lag between disclosure and vendor patch in consumer router firmware routinely exceeds 90 days, and downstream products may remain vulnerable far longer.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-71984 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data