# CVE-2026-115724: VLC for Android before 3.7.2 File Overwrite via Spoofed Mail Attachment Provider


- **Severity:** Low 2.1 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-7vgw-xvvg-pq6r

## What is CVE-2026-115724?

CVE-2026-115724 is a low-severity vulnerability in VideoLAN VLC for Android, published on 23 Oct 2026. 

### Official description

VLC for Android before 3.7.2 contains a confused-deputy file overwrite vulnerability in FileUtils.getUri() that trusts content URIs based only on the com.fsck.k9.attachmentprovider or gmail-ls authority. A co-installed app without permissions can declare these authorities and send a crafted VIEW intent to the exported StartActivity, making VLC write attacker-chosen content under an attacker-chosen name in the shared Download directory, overwriting other apps' files when VLC holds All files access.

Weakness: CWE-346 (Origin Validation Error)

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


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

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

## Is CVE-2026-115724 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115724 is a low-severity vulnerability in VideoLAN VLC for Android, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115724 in the wild and no public exploit code.

Affected product: VideoLAN VLC for Android. 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-115724/ (Markdown: https://insights.sbomify.com/CVE-2026-115724/index.md)
```

## Sources

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

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