CVE-2026-49194
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 · uneditedThe debugging routine SCREEN_CLICK(5053) enables a connection to skip the standard device login prompt entirely and directly enter an interactive shell interface.
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 · moderate confidenceThis is an authentication bypass vulnerability in a debugging routine (SCREEN_CLICK(5053)) that allows connections to circumvent the standard device login prompt and directly access an interactive shell interface. The vulnerability provides unauthenticated attackers with full shell access, representing a critical security failure in the authentication mechanism.
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<= m6e_ai_1.00.000019CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 installed firmware versionAccess the device admin web interface or console and locate the firmware version, typically found in Settings > System > Firmware Version, or run 'cat /etc/version' or 'nvram get firmware_version' if console access is availableAffected if The firmware version is m6e_ai_1.00.000019 or any earlier version (any version <= m6e_ai_1.00.000019)
-
Locate the SCREEN_CLICK debugging routineIf firmware extraction is possible, search the firmware binary for the string 'SCREEN_CLICK' or function ID 5053, or probe the device network services for debug interfaces that may be listeningAffected if The SCREEN_CLICK(5053) routine is present in the firmware build and exposed via a network service or debug interface
-
Test for unauthenticated shell accessAttempt to connect to the suspected debug port (commonly port 5053 or similar debug ports on the device) using telnet or netcat without providing any credentials: 'telnet <device_ip> 5053'Affected if An interactive shell prompt is returned without being prompted for login credentials
-
Verify network exposure of debug interfaceScan the device for open ports using 'nmap <device_ip>' or 'netstat -tuln' on the device itself, specifically looking for the port associated with the SCREEN_CLICK routineAffected if The debugging interface port (such as 5053) is open and accessible from the network without authentication
The device is affected if it runs Acer Connect M6e 5g firmware version m6e_ai_1.00.000019 or earlier AND the SCREEN_CLICK(5053) debugging routine is present and accessible without requiring authentication.
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 SCREEN_CLICK(5053) debugging routine in production environments and ensure all authentication mechanisms are enforced before shell access is granted. Implement proper access controls to prevent unauthenticated access to debugging functions.
- Consultation8.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49194 — 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-49194 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