# CVE-2026-38093: Path traversal in n/a

> A malicious Android app can exploit path traversal in the Flutter file picker to create arbitrary files in the victim app's internal storage.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A: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:** 28 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-r2rg-pm28-j8gw

## What is CVE-2026-38093?

CVE-2026-38093 is a low-severity path traversal vulnerability in n/a, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

file_picker (aka flutter_file_picker) for Flutter, all versions through 10.3.10, is vulnerable to path traversal (CWE-22) in its Android implementation. The openFileStream() method in FileUtils.kt uses the DISPLAY_NAME obtained from ContentResolver.query() directly in file path construction without sanitization. A malicious Android app with a crafted ContentProvider can return a filename containing ../ sequences, causing the plugin to create arbitrary files and directories outside the intended cache directory within the victim app's internal storage. Existing files are not overwritten due to an existence check.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-38093 being exploited?

There is no known exploitation of CVE-2026-38093 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-38093 is a low-severity path traversal vulnerability in n/a, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-38093 in the wild and no public exploit code.

Affected product: n/a. 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-38093/ (Markdown: https://insights.sbomify.com/CVE-2026-38093/index.md)
```

## Sources

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

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