CVE-2026-50211 is a critical (CVSS 9.8) flaw in Acer Connect M6E 5G firmware. Leftover engineering and factory diagnostic software remains on retail builds and lets a malicious app write to internal NVRAM registers. The record lists no fixed version, so check Acer's advisory.
What's affected
- Product: Acer Connect M6E 5G, hardware and firmware.
- Fixed version: not stated in the CVE record. Check Acer's advisory (article 19707).
- Weakness: CWE-134, use of an externally controlled format string (the record's classification, which fits the description loosely).
- CVSS 9.8 (critical), vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. - Published 4 June 2026. Not marked as exploited in CISA KEV.
How to check if you're exposed
Acer ships these devices as consumer networking hardware, so there is no package manager to query. Use the device itself.
- Log in to the Acer Connect M6E 5G admin page or the Acer Connect app and note the firmware version shown in the device or system information screen.
- Open the Acer advisory named in the Sources section and compare your version with the fixed firmware it lists.
- If the admin page or any service on the device is reachable from the internet, treat that as a separate problem and close it, whatever the firmware version.
If you run phone or tablet apps that connect to the device, keep them to apps you trust until the firmware is updated. The record talks about malicious apps, so the app side matters here.
What to do now
- Open the Acer advisory (knowledge base article 19707) and confirm which Acer Connect M6E 5G firmware fixes this CVE. The CVE record does not name a fixed version, so do not assume one.
- Install the fixed firmware through the vendor update path as soon as it is available for your unit.
- Until then, keep the admin interface off the internet and limit it to a trusted management network.
- Change any password or key that was stored on or sent through the device if you think it may have been exposed.
- Add the device to your asset inventory with its firmware version so the next advisory is easy to match.
Why it matters
Factory tooling exists so manufacturers can set up and test hardware. It should be stripped from the retail image. When it is not, an ordinary user-level program may reach functions that were never meant to be exposed, and here the record says those functions can write to NVRAM registers, which hold low-level device configuration.
The takeaway for anyone shipping devices is a release checklist item: confirm that diagnostic interfaces are removed or locked before the production build is signed.
Quick check
Why does the CWE look odd for this description?
CVE records are sometimes classified loosely by the numbering authority. Trust the description for what is wrong, and the vendor advisory for the fix.
Sources
- Acer knowledge base article 19707 (named in the CVE record; the page was behind a browser check when I tried to read it, so the details here come from the CVE record)
- Safeguard Gold entry
Last reviewed: 19 October 2026.
