CVE-2026-50214 is a critical (CVSS 9.8) flaw in the Acer Connect M6E 5G ecosystem. The /v1/Plan service relies on one shared global API token for full administrative management, which allows arbitrary creation of zero-cost network access plans. The record names 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-345, insufficient verification of data authenticity.
- 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.
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
One token that controls everything is a single point of failure. If it leaks, every account and plan on the service is in reach, and nothing ties a request back to a person. The record describes how that can be turned into free access plans, which is a billing problem as much as a security one.
Better designs scope tokens per user and per action, rotate them, and log who used them. The weakness class is CWE-345: the service accepts a credential without checking that it proves the right thing.
Quick check
Can I fix this myself?
The shared token lives on the vendor side of the service, so the fix has to come from Acer. Your part is applying firmware and keeping the device off untrusted networks.
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.
