Backend key disclosure via verbose error pages
Published Jun 4, 2026 · Updated Jun 4, 2026
Improper authentication in Acer Connect M6E firmware through M6E_AI_1.00.000019 allows remote attackers to obtain backend API keys. The production M3WebServer embeds static backend API keys and exposes them in verbose error pages instead of containing the secrets. No authentication or user interaction is required; Acer has not disclosed which backend operations the exposed keys authorize.
Summary
What happened
Improper authentication in Acer Connect M6E firmware through M6E_AI_1.00.000019 allows remote attackers to obtain backend API keys. The production M3WebServer embeds static backend API keys and exposes them in verbose error pages instead of containing the secrets. No authentication or user interaction is required; Acer has not disclosed which backend operations the exposed keys authorize.
The record
- CVE
- CVE-2026-49191
- Published
- Jun 4, 2026
- Updated
- Jun 4, 2026
- Vendor
- Acer Inc.
- Product
- Acer Connect M6E 5G Mobile WiFi
- Classifications
- CWE-287, CAPEC-204, T1552
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 4, 2026CVE publishedPublication date reported by the CVE source.
- Jun 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=* <=M6E_AI_1.00.000019
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo