Arbitrary file creation via unsanitized display name
Published Aug 28, 2026 · Updated Aug 28, 2026
Path traversal in file_picker 10.3.10 and earlier allows local users to create files and directories in a victim Android app's storage. FileUtils.openFileStream concatenates an untrusted DISPLAY_NAME from ContentResolver.query into a cache path without sanitizing traversal sequences. Exploitation requires an installed malicious ContentProvider app to be selected as the file source; existing files are not overwritten.
Summary
What happened
Path traversal in file_picker 10.3.10 and earlier allows local users to create files and directories in a victim Android app's storage. FileUtils.openFileStream concatenates an untrusted DISPLAY_NAME from ContentResolver.query into a cache path without sanitizing traversal sequences. Exploitation requires an installed malicious ContentProvider app to be selected as the file source; existing files are not overwritten.
The record
- CVE
- CVE-2026-38093
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-22
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 28, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub issue 1967 reproduction procedureproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo