Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-84283 Overview
CVE-2026-84283 affects Secure Folder 1.2, an Android application that advertises password-protected vault functionality. The application stores files added to its vault as unencrypted objects within the Android shared-storage tree. Any local application or file manager with access to the relevant shared-storage path can enumerate, copy, and open those files without authenticating to Secure Folder. The weakness is categorized under CWE-922: Insecure Storage of Sensitive Information.
Critical Impact
A local app with shared-storage read permission can bypass Secure Folder's password gate and exfiltrate every file placed in the vault.
Affected Products
- Secure Folder 1.2 for Android (Google Play listing)
- Android devices where the app has write access to shared storage
- Any device profile where third-party apps hold READ_EXTERNAL_STORAGE or equivalent scoped-storage access
Discovery Timeline
- 2026-09-25 - CVE CVE-2026-84283 published to NVD
- 2026-09-25 - Last updated in NVD database
- Advisory published by Fluid Attacks under the identifier Sanguisugabogg
Technical Details for CVE-2026-84283
Vulnerability Analysis
Secure Folder 1.2 presents itself as a password-protected vault for sensitive files on Android. The protection model relies solely on the application's own UI authentication check. The underlying files are not encrypted at rest and are written to a world-readable location within Android shared storage. Any process holding storage read permission can enumerate those files directly through the file system, bypassing the vault UI entirely. The password prompt therefore does not act as a security boundary for the stored data.
The advisory from Fluid Attacks confirms the files remain in cleartext within the shared-storage tree after being added to the vault. Confidentiality is fully impacted for every file the user believed to be protected, while integrity and availability of the host system remain unaffected.
Root Cause
The root cause is a design flaw mapped to [CWE-922]. The application fails to apply cryptographic protection or scoped private storage to vault contents. Instead of using the Android app-private directory under /data/data/<package>/ or encrypting with the Android Keystore, Secure Folder keeps the originals in shared storage.
Attack Vector
Exploitation requires local access and low privileges. An attacker's app, a file manager, a cloud sync tool, or a malicious SDK embedded in another app can read the vault directory with standard storage permissions. No interaction with Secure Folder itself is required. The attacker enumerates the directory, copies files to attacker-controlled storage, and reads them without any password prompt. The vulnerability is described in prose only; no public proof-of-concept exploit code is linked in the advisory.
Detection Methods for CVE-2026-84283
Indicators of Compromise
- Third-party apps on the device reading from the Secure Folder shared-storage path without launching the Secure Folder app
- Unexpected outbound uploads from file manager or cloud-sync apps containing filenames previously added to the vault
- New applications requesting broad READ_EXTERNAL_STORAGE or MANAGE_EXTERNAL_STORAGE permissions shortly after Secure Folder installation
Detection Strategies
- Inventory Android devices in managed fleets for the package com.securefolder.securevault
- Use mobile threat defense (MTD) or mobile device management (MDM) tooling to flag apps that store sensitive content in shared storage rather than app-private directories
- Audit app permission grants to identify processes with broad storage access that could reach the vault path
Monitoring Recommendations
- Monitor DLP or cloud-upload telemetry for files sourced from the Secure Folder path
- Alert on new installs of Secure Folder 1.2 through MDM compliance policies
- Track permission changes that grant storage access to newly installed apps on devices holding sensitive data
How to Mitigate CVE-2026-84283
Immediate Actions Required
- Stop using Secure Folder 1.2 to store sensitive files until a fixed version is released
- Move existing vault contents to a vetted encrypted container or to Android's built-in secure storage features
- Review and revoke broad storage permissions granted to unnecessary third-party apps on affected devices
Patch Information
No vendor patch is referenced in the NVD entry or the Fluid Attacks advisory at the time of publication. Users should monitor the Google Play listing and the Fluid Attacks advisory for updates.
Workarounds
- Uninstall Secure Folder 1.2 and migrate sensitive files to a vendor-supported encrypted vault
- Restrict installation of apps requesting MANAGE_EXTERNAL_STORAGE through MDM policy
- On managed devices, enforce work-profile separation so that personal apps cannot read corporate storage locations
# MDM policy example: block the affected package via Android Enterprise
adb shell pm uninstall --user 0 com.securefolder.securevault
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

