Improper export of android application components in CoverScreenWidgetActionActivity in Samsung Contacts prior to SMR Nov-2026 Release 1 allows local attackers to make a call without proper permission.
Improper export of android application components in CoverScreenWidgetActionActivitySmall in Samsung Contacts prior to SMR Nov-2026 Release 1 allows local attackers to make a call without proper permission.
Improper export of android application components in CoverScreenWidgetActionActivityLarge in Samsung Contacts prior to SMR Nov-2026 Release 1 allows local attackers to make a call without proper permission.
A potential vulnerability was reported in some Lenovo Tablets that could allow a third-party application to perform an arbitrary file write with elevated privileges.
A potential improper permissions vulnerability was reported in Lenovo XiangBangbang that could allow a local application to perform unauthorized touch gestures.
CVE-2026-21127 is a vulnerability in Samsung Account prior to version 15.7.01.1 where improper export of Android application components allows local attackers to access sensitive data. The issue is classified under CWE-926, indicating improper export of components. The vulnerability has a CVSS 4.0 base score of 6.9, reflecting a medium severity level. No patch or remediation details are provided in the available data.
Acode is a powerful text and code editor for Android. From 1.11.6 until 1.12.7, com.foxdebug.acode.rk.exec.terminal.TerminalService is declared as an exported service in src/plugins/terminal/plugin.xml without a binding permission, and src/plugins/terminal/src/android/TerminalService.java does not verify the caller. Any installed Android application can bind the service and send MSG_EXEC with an attacker-controlled cmd value, which the terminal implementation passes to ProcessBuilder with sh -c inside Acode's UID. This allows a zero-permission local application to execute commands with access to Acode private data, remote credentials, Storage Access Framework grants, and runtime permissions without additional interaction at attack time. This issue is fixed in version 1.12.7.
Ekia File Manager 1.2.7 exposes com.ekia.filecontrolmanager.OpenFileProvider as an exported Android ContentProvider without requiring caller permissions.
The provider maps the caller-controlled URI path directly to a filesystem path and passes it to new File(...). It then supports query(), openFile(), and delete() operations. Because the provider is exported and lacks android:permission, android:readPermission, or android:writePermission, another local application can access the provider authority and cause File Manager's process to read, create, overwrite, or delete files that are accessible to that process.
CVE-2026-18994 is a high-severity vulnerability in the Lenovo File Manager Android Application, distributed exclusively in the Chinese market. It involves improper authorization due to improper export of application components, allowing a local authenticated user to read or modify protected files within the app. The affected versions are all versions prior to 9.8.1.77. There is no information about an available patch or official fix at this time.
CVE-2026-21113 is a medium severity vulnerability in Samsung Mobile's Visual Voicemail application prior to version 20.1.00.05. It involves improper export of Android application components, which allows local attackers to initiate calls without having the proper permissions.
CVE-2026-21108 is a vulnerability in Samsung Mobile's Bixby Touch application prior to version 4.3.01.17. It involves improper export of Android application components, which allows local attackers to access sensitive information. The vulnerability has a medium severity with a CVSS score of 6.9. No public exploits or patches are currently documented.
In MiracastService, there is a possible escalation of privilege due to a confused deputy. This could lead to local denial of service with User execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS11060069 / DTV04881615; Issue ID: MSV-7882.
CVE-2026-21081 is a medium severity vulnerability in SamsungPassAutofill prior to version 5.2.10. It involves improper export of Android application components, which allows local attackers to access sensitive information. Exploitation requires user interaction. No official patch or remediation guidance is currently confirmed.
CVE-2026-21063 is a medium severity vulnerability in Samsung Mobile Devices related to improper export of Android application components in the AppLock feature prior to the SMR Aug-2026 Release 1. This flaw allows physical attackers to bypass the app lock function, potentially exposing locked applications. The vulnerability is identified as CWE-926, indicating improper export of components. No specific affected versions are provided, and no official patch or remediation guidance is currently available.
CVE-2026-21059 is a medium severity vulnerability affecting Samsung Contacts on Samsung Mobile Devices prior to the SMR Aug-2026 Release 1. It involves improper export of Android application components, which allows local attackers to delete files with the privileges of the Samsung Contacts app.
In versions of the Datadog Android application prior to v545-5.9.2, six App Widget configuration activities (IncidentWidgetActivity, MonitorSavedViewWidgetActivity, OnCallShiftsWidgetActivity, OnCallPagesWidgetActivity, SloWidgetActivity, DashboardWidgetActivity) are exported with no permission guard. Each accepts a caller-supplied AppWidgetManager.EXTRA_APPWIDGET_ID and, when no deep-link destination is resolved, uses it to load the matching widget's stored session and automatically log in as that user. Because Android widget IDs are small sequential integers, a co-installed application can brute-force this value to find one that matches a widget configured on the victim's device.
This requires:
A malicious application co-installed on the victim's device.
At least one of the six widgets configured on the victim's home screen.
An active Datadog session cached locally.
Impact: The matching configuration activity opens in the foreground under the victim's session and renders live infrastructure data. Exposure is limited to a visual side channel (e.g., screen recording or accessibility services); the calling application cannot programmatically read the rendered data.
In versions of the Datadog Android application prior to v541-5.9.2, the exported launcher activity AppActivity accepts an attacker-supplied session (including OAuth tokens) from Intent extras with no permission guard, and signs the app into that session without validating it against the backend.
This requires a malicious application co-installed on a device with the Datadog app installed, and an OAuth token the attacker is willing to load into the victim's app.
Impact: A co-installed application can switch the victim's Datadog app to a session the attacker controls. This is an account-confusion issue; it does not by itself expose the victim's existing session or data.
In versions of the Datadog Android application prior to v541-5.9.2, BubbleChatActivity is exported with no permission guard and accepts a SEND intent with a caller-supplied conversation_id. When the activity closes and no in-process session matches that ID, it unconditionally cancels notification ID 9201 (the Bits AI chat notification), with no check on the caller's identity or ownership of the conversation.
This requires a malicious application co-installed on the victim's device.
Impact: A co-installed application can silently dismiss the victim's Bits AI chat notification. No chat content is exposed; conversation data remains server-authentication gated and is never returned to the caller.