Cyber Resilience

CVE-2026-57848

Public PoC
Published
18 July 2026
Modified
23 July 2026
CVSS Score v4 6.8
Click a component to see what it means
Raw vectorCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0014 4th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-57848 is a medium-severity Improper Export of Android Application Components (CWE-926) vulnerability. Its CVSS base score is 6.8 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Inter-Process Communication (T1559); ranked at the 4th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1559 Inter-Process Communication Execution
Adversaries may abuse inter-process communication (IPC) mechanisms for local code or command execution.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-8207Shared CWE-926
CVE-2025-8258Shared CWE-926
CVE-2025-9093Shared CWE-926
CVE-2025-9672Shared CWE-926
CVE-2025-7940Shared CWE-926
CVE-2025-9677Shared CWE-926
CVE-2025-10722Shared CWE-926
CVE-2023-41827Shared CWE-926
CVE-2025-9097Shared CWE-926
CVE-2024-3479Shared CWE-926

Affected Assets

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

AC-3 directly requires enforcement of authorizations on logical access, which stops an exported Android component from being reachable without proper restrictions.

Least privilege reduces the exposure of exported components by limiting unnecessary authorizations granted to other apps.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 mostly match
prevents

Defining and enforcing least-privilege access permissions directly prevents unauthorized export of Android components.

PR.PS-06 mostly match
prevents

Secure SDLC practices include configuring component exports and permission checks to avoid this weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure-coding standards require explicit permission declarations and intent-filter restrictions to avoid improper exports.

finds

Security testing can detect exported components lacking proper restrictions, providing partial coverage of the weakness.

prevents

Enforcing information-access restrictions on exported Android components directly prevents unauthorized launch or data access.

prevents

Defining application security requirements includes specifying proper export restrictions and permission checks for components.

prevents

Secure architecture principles discourage overly permissive component exports, though the control is broader than this single weakness.

References