CVE-2026-49195
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 · uneditedUnauthenticated Debug Service. The /sbin/mtk_dut binary is exposed on TCP port 9000 without authentication, allowing any LAN-based attacker to execute arbitrary UCC commands.
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 confidenceAn unauthenticated debug service exists in the /sbin/mtk_dut binary exposed on TCP port 9000. This allows any attacker with LAN access to execute arbitrary UCC commands without any authentication, providing privileged access to device functions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= w6x_gbl_2.00.000005CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/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.
-
Identify the device model and firmware versionLog into the router admin panel or check the device label to confirm it is an Acer Predator Connect W6x. Determine the firmware version (typically found in Settings > System > Firmware Version or similar).Affected if The device is an Acer Predator Connect W6x with firmware version w6x_gbl_2.00.000005 or earlier.
-
Verify port 9000 is open and listeningFrom a machine on the same LAN, run a port scan against the router's IP address targeting TCP port 9000 (e.g., nmap -p 9000 <router_ip> or telnet <router_ip> 9000).Affected if Port 9000 returns as open or accepts a connection, indicating the debug service is exposed.
-
Check for the mtk_dut binary presenceIf you have shell access (via SSH, Telnet, or UART console on the device), run ls -la /sbin/mtk_dut to verify the binary exists.Affected if The file /sbin/mtk_dut exists on the device filesystem.
-
Confirm the debug service is runningIf you have shell access, run ps | grep mtk_dut or check /proc/<pid>/cmdline to see if the mtk_dut process is active and listening on port 9000.Affected if The mtk_dut process is running and bound to port 9000.
If the device is an Acer Predator Connect W6x running firmware w6x_gbl_2.00.000005 or earlier AND port 9000 is exposed on the LAN, the environment is affected by this 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 dataDisable or remove the mtk_dut debug service if not required, or implement authentication and network access controls to prevent unauthorized LAN access to port 9000.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49195 — 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-49195 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