Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessInstall app or file manager with shared-storage access
-
ExploitEnumerate Secure Folder's shared-storage path
-
ExecutionRead/copy unencrypted vault files
-
ImpactExfiltrate protected data without vault password
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Secure storage of sensitive data
|
| Exploitation Conditions | Requires local presence on the same Android device: a second application or file manager that holds read access to the shared-storage path where Secure Folder 1.2 writes vaulted files. Exploitation is limited by needing that co-resident app/permission (PR:L, AV:L) and the presence of Android runtime/scoped-storage permissions; there is no remote or network vector, and only confidentiality is affected (files can be read/copied, not modified through this flaw). The core enabling condition is design behavior, not a special setting - the vault stores selected files unencrypted by default, so any deployment of version 1.2 that has files added to the vault is affected. |
| Impact | This is a low-to-moderate real-world risk despite the 6.8 CVSS 4.0 score. The vendor vector (AV:L/AC:L/AT:N/PR:L/UI:N/VC:H) correctly frames this as a LOCAL confidentiality-only exposure: an attacker must already have code (a malicious/nosy app) or a file manager running on the same device with access to the shared-storage path - there is no network reach. There is no EPSS score, no CISA KEV listing, and no public exploit code provided, so the exploitation status is 'no public exploit identified at time of analysis.' The single high signal is technical impact (VC:H): the flaw fully defeats the app's core promise of a 'password-protected vault' because the underlying files are never encrypted. Countering that, the affected product is an obscure third-party Android app with a tiny footprint, and exploitation requires prior local presence, so this is a genuine-but-narrow issue rather than a mass-exploitation priority. Note the tags list 'Google' and 'Hashicorp' as vendors, which is inconsistent with the description - the app is an independent developer's product merely hosted on Google Play and has no HashiCorp relationship; treat those vendor associations as unreliable. |
| Exploit ScenarioDerived | A user installs a seemingly benign app (or connects a file manager) that holds Android shared-storage read permission. Because Secure Folder 1.2 saves 'vaulted' files unencrypted in shared storage, that app silently enumerates and copies the supposedly protected documents/photos without ever prompting for the vault password. No public PoC is referenced, but the technique is trivial given local storage access. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 25, 2026
Secure Folder 1.2, an Android vault app distributed as com.securefolder.securevault on Google Play, stores files selected for its password-protected vault as unencrypted files inside the Android shared-storage tree, so any co-resident application or file manager holding read access to that path can enumerate, copy, and open the vaulted files without authenticating to Secure Folder. The exposure is strictly local: the CVSS 4.0 vector requires local access with low privileges (AV:L, PR:L) and no user interaction, and impact is confidentiality-only, matching our independent CVSS 3.1 assessment (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), which characterizes real-world risk as low-to-moderate despite the 6.8 base score. There is no public exploit identified at time of analysis and no CISA KEV listing, so this is a design-level information disclosure rather than an actively attacked flaw. Any deployment of version 1.2 with files added to the vault is affected by default, since the plaintext storage behavior is not the result of an optional setting.
RemediationAI
No vendor-released patch was identified at time of analysis, and the provided references contain no fixed version, commit, or vendor advisory beyond the Fluid Attacks write-up at https://fluidattacks.com/advisories/sanguisugabogg, so the exact fix version cannot be cited. Until the developer moves vault contents into app-private internal storage (or encrypts them with a key derived from the user's passphrase before writing to shared storage), the actionable mitigations are: remove any sensitive files from the Secure Folder vault and store them instead in an app that keeps data in its private sandbox or in a hardware-backed encrypted container; if vault use must continue, treat every file placed in it as publicly readable and avoid adding credentials, ID scans, or personal documents; revoke storage permissions (READ_EXTERNAL_STORAGE, MANAGE_EXTERNAL_STORAGE, and the legacy 'All files access' toggle) from untrusted or unnecessary apps via Settings > Apps > Special access, accepting that this will break file managers, gallery sync, and backup clients that depend on those permissions; and on managed fleets, use an Android work profile or MDM policy to block installation of the app or to constrain which apps can hold broad storage access, with the trade-off of reduced user flexibility and possible breakage of legitimate storage-dependent tooling. Note that device encryption does not meaningfully mitigate this flaw while the device is unlocked and in use, and uninstalling Secure Folder after vaulting files does not guarantee the plaintext copies are erased from shared storage, so manual deletion of the copied files under the shared-storage path should be verified.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-922 (Insecure Storage of Sensitive Information): Secure Folder implements its 'password-protected vault' as an application-layer access control only, while the underlying file bytes are written in cleartext to Android's shared/external storage (the /sdcard or /storage/emulated/0 tree) instead of the app's private internal sandbox (getFilesDir()/getCacheDir()). On modern Android the shared-storage tree is governed by scoped storage and mediastore semantics, but files placed there remain readable by other apps that hold READ_EXTERNAL_STORAGE, MANAGE_EXTERNAL_STORAGE, or legacy broad storage permissions, and they are also reachable through USB/MTP access, backup tooling, and any file manager the user has installed. Because the files are not encrypted at rest, the app's password prompt can be bypassed entirely by reading the path directly, and device-level full-disk or file-based encryption does not mitigate the issue in a running, unlocked device session. No CPE entries were supplied in the input data; the confirmed affected artifact is the Android application Secure Folder 1.2 (package id com.securefolder.securevault) as listed on Google Play, with the Fluid Attacks advisory (help@fluidattacks.com) serving as the reporting reference.
Know when Android gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Local co-resident app with shared-storage access (AV:L, PR:L) reads unencrypted vault files with no user interaction; full confidentiality loss but no integrity or availability impact.
Primary rating from Vendor (fluidattacks).
CVSS VectorVendor: fluidattacks
DescriptionCVE.org
Secure Folder 1.2 stores files selected for its password-protected vault as unencrypted files in the Android shared-storage tree. A local application or file manager that has access to the relevant shared-storage path can enumerate, copy, and open those files without authenticating to Secure Folder.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows and OS X and before 11.2.202.466
Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in A
Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly imp
Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android bef
Apktool versions 2.9.1 and prior contain a path traversal vulnerability when processing Android APK files. Malicious APK
An elevation of privilege vulnerability in the Android system (art). Rated high severity (CVSS 7.8), this vulnerability
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows
luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.
The Broadcom Wi-Fi driver in the kernel in Android 4.x before 4.4.4, 5.x before 5.1.1 LMY49G, and 6.x before 2016-02-01
EUVD-2026-86481
GHSA-vx3q-gcj3-hmg7
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB