CVE-2026-57848: Improper Export of Android Application Components in stoatchat Stoat for Android
Stoat for Android exports the chat.stoat.activities.ShareTargetActivity component (reachable to any process on the device via the android.intent.action.SEND intent) and accepts the file to share as a URI supplied through the android.intent.extra.STREAM extra. The activity does not validate or filter the incoming URI before using it as the outgoing attachment, so a caller can pass a file:// URI pointing at the application's own internal storage (for example /data/data/chat.revolt/databases/revolt.db, cached authentication token files, or preferences) and have the app treat that internal file as a user-selected attachment. An attacker who can invoke intents on the victim's device (via ADB access, a co-installed malicious application, or any other route that reaches Android's intent dispatch) can launch ShareTargetActivity with such a URI and cause the victim, on a single channel-selection interaction, to send the internal file to any Stoat channel or user of the attacker's choosing. The composer displays the attachment as \"attachment\" with no filename indication, so the victim has no visible signal that the file being sent is their own internal application data. Consequences include disclosure of the local Stoat database (message history, contact list, cached content), disclosure of authentication tokens permitting full account takeover, and disclosure of any other file readable by the app process.
AI Analysis
Technical Summary
The vulnerability in Stoat for Android involves the exported ShareTargetActivity component that handles the android.intent.action.SEND intent with a file URI passed via android.intent.extra.STREAM. The activity fails to validate or filter the incoming URI, allowing an attacker with the ability to send intents on the victim's device to specify internal file URIs (e.g., app databases, cached tokens). When the victim selects a channel to share with, the app sends the internal file as an attachment without user-visible indication of its sensitive nature. This results in unauthorized disclosure of internal application data and authentication tokens, enabling potential account compromise.
Potential Impact
An attacker capable of invoking intents on the victim's device can cause the victim to unknowingly send sensitive internal files to attacker-controlled channels. This can disclose the local Stoat database containing message history, contacts, cached content, and authentication tokens. Disclosure of authentication tokens can lead to full account takeover. The vulnerability does not affect availability or integrity but has a high confidentiality impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict or monitor applications and processes that can send intents to Stoat for Android, and limit ADB or other access that could be used to invoke intents maliciously. Users should be cautious about co-installed apps that might exploit this behavior.
CVE-2026-57848: Improper Export of Android Application Components in stoatchat Stoat for Android
Description
Stoat for Android exports the chat.stoat.activities.ShareTargetActivity component (reachable to any process on the device via the android.intent.action.SEND intent) and accepts the file to share as a URI supplied through the android.intent.extra.STREAM extra. The activity does not validate or filter the incoming URI before using it as the outgoing attachment, so a caller can pass a file:// URI pointing at the application's own internal storage (for example /data/data/chat.revolt/databases/revolt.db, cached authentication token files, or preferences) and have the app treat that internal file as a user-selected attachment. An attacker who can invoke intents on the victim's device (via ADB access, a co-installed malicious application, or any other route that reaches Android's intent dispatch) can launch ShareTargetActivity with such a URI and cause the victim, on a single channel-selection interaction, to send the internal file to any Stoat channel or user of the attacker's choosing. The composer displays the attachment as \"attachment\" with no filename indication, so the victim has no visible signal that the file being sent is their own internal application data. Consequences include disclosure of the local Stoat database (message history, contact list, cached content), disclosure of authentication tokens permitting full account takeover, and disclosure of any other file readable by the app process.
CVSS v3.1
Score 5.5medium
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Stoat for Android involves the exported ShareTargetActivity component that handles the android.intent.action.SEND intent with a file URI passed via android.intent.extra.STREAM. The activity fails to validate or filter the incoming URI, allowing an attacker with the ability to send intents on the victim's device to specify internal file URIs (e.g., app databases, cached tokens). When the victim selects a channel to share with, the app sends the internal file as an attachment without user-visible indication of its sensitive nature. This results in unauthorized disclosure of internal application data and authentication tokens, enabling potential account compromise.
Potential Impact
An attacker capable of invoking intents on the victim's device can cause the victim to unknowingly send sensitive internal files to attacker-controlled channels. This can disclose the local Stoat database containing message history, contacts, cached content, and authentication tokens. Disclosure of authentication tokens can lead to full account takeover. The vulnerability does not affect availability or integrity but has a high confidentiality impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict or monitor applications and processes that can send intents to Stoat for Android, and limit ADB or other access that could be used to invoke intents maliciously. Users should be cautious about co-installed apps that might exploit this behavior.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-06-25T18:48:00.282Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a5bd7272a4a8d59892ef2c8
Added to database: 07/18/2026, 19:42:31 UTC
Last enriched: 07/25/2026, 22:47:28 UTC
Last updated: 08/30/2026, 22:52:12 UTC
Views: 81
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.