CVE-2026-53876
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 · uneditedRadiX AX6600 WiFi 6 Tri-Band Gaming Router contains an OS command injection vulnerability, which may lead to arbitrary command execution with the root privilege by a user who logs in to the web console as an administrator.
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 analysis · high confidenceThe RadiX AX6600 router has an OS command injection vulnerability in its web console administrative interface. An authenticated administrator can inject arbitrary OS commands that execute with root privileges due to insufficient input sanitization when processing user-supplied values in backend system calls.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is RadiX AX6600Access the router administrative web interface or check the device label/marketing materials to verify the exact model numberAffected if The device is NOT a RadiX AX6600 router (different models may have different vulnerabilities)
-
Identify installed firmware versionLog into the router web administrative console and navigate to System Settings or Administration > Firmware Upgrade to view the current firmware version; alternatively, check the vendor support page for the deviceAffected if The installed firmware version has not been patched by the vendor for this command injection vulnerability
-
Verify web administrative interface is enabledAccess the router login page at the default gateway IP (typically 192.168.1.1 or 192.168.0.1) using a web browser to confirm the administrative interface is accessibleAffected if The web administrative interface is exposed to untrusted networks (such as the public internet) rather than only being accessible from trusted local networks
-
Review administrative access controlsCheck the router security settings to determine if remote administration is enabled and from which IP addresses it can be accessed; look for settings like 'Remote Management' or 'Admin Access' in the web consoleAffected if Remote administrative access is permitted from any IP address or from untrusted networks
-
Examine system logs for suspicious administrative activityIn the router web console, navigate to System Logs or Security Logs and look for unexpected administrative login events, particularly from unfamiliar IP addresses or at unusual timesAffected if There are administrative login events that you do not recognize or that originate from unexpected sources
You are likely affected if you are running a RadiX AX6600 router with the web administrative interface accessible and the firmware has not been updated to address this OS command injection vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the vendor firmware patch when available; until then, limit administrative web console access to trusted IPs only and monitor for unauthorized administrative sessions.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-53876 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-53876 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