CVE-2026-49189
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 · uneditedUnchecked public access permissions on a core Broadcast Receiver allow unauthorized local software components to invoke administrative operations.
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 confidenceA Broadcast Receiver component lacks proper permission checks, allowing any locally installed application to send broadcasts that trigger administrative operations without authorization. This is a classic Android permission bypass where the receiver is either exported without protection or doesn't validate the caller's permissions before executing privileged operations.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Check device firmware versionRun 'adb shell getprop ro.build.version.release' or 'adb shell getprop ro.build.display.id' to retrieve the installed firmware versionAffected if The firmware version is m6e_ai_1.00.000019 or lower
-
Identify vulnerable Broadcast ReceiverUse 'adb shell pm dump <package_name> | grep -A 20 BroadcastReceiver' to examine receiver declarations in the manifest, or decompile the system APK containing the receiver and inspect AndroidManifest.xml for the exported receiverAffected if A BroadcastReceiver is declared with android:exported="true" or missing android:permission attribute, and it handles administrative operations
-
Verify permission protection levelIn the receiver's manifest entry, check for android:permission attribute; if absent or set to a low-protection permission (like 'android.permission.INTERNET' or no permission), the receiver is unprotectedAffected if The receiver has no android:permission attribute or uses a permission with protectionLevel="normal" or "dangerous" instead of "signature"
-
Confirm receiver handles privileged operationsDecompile the receiver's APK and inspect the onReceive method code for system administrative functions such as Settings.Secure modifications, user account management, or device policy operationsAffected if The receiver executes privileged administrative operations without additional permission validation in code
The device is affected if running Acer Connect M6e 5g firmware <= m6e_ai_1.00.000019 AND contains a Broadcast Receiver that is exported without signature-level permission protection and can trigger administrative operations.
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 dataImplement proper permission enforcement on the Broadcast Receiver by requiring a signature-level or system-level permission, or by adding explicit permission checks within the receiver's onReceive method before executing administrative operations.
- Consultation3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49189 — 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-49189 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