# CVE-2026-84283: FluteCode Secure Folder 1.2 -Plaintext vault files in shared storage bypass the PIN gate

> Local attackers can access sensitive vault files without authentication because the application stores them unencrypted in shared storage.

- **Severity:** Medium 6.8 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-vx3q-gcj3-hmg7

## What is CVE-2026-84283?

CVE-2026-84283 is a medium-severity vulnerability in FluteCode Secure Folder, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-922 (Insecure Storage of Sensitive Information)

## Which versions are affected by CVE-2026-84283?


## How do I fix CVE-2026-84283?

No fix has been published for CVE-2026-84283 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-84283 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-84283 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-84283 and fix it if it is affected.

What it is: CVE-2026-84283 is a medium-severity vulnerability in FluteCode Secure Folder, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-84283 exists.

Affected product: FluteCode Secure Folder. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-84283/ (Markdown: https://insights.sbomify.com/CVE-2026-84283/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-84283
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-84283
- OSV: https://osv.dev/vulnerability/CVE-2026-84283

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-84283/
Summaries are generated and may contain mistakes; the official description above is the record.