# CVE-2025-20926: Missing authorization in Samsung My Files

> Local attackers can access files with elevated privileges due to improper component export in the Samsung My Files application.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 6 Mar 2025
- **Updated:** 6 Mar 2025
- **Also known as:** GHSA-8m69-67p7-65wf

## What is CVE-2025-20926?

CVE-2025-20926 is a medium-severity missing authorization vulnerability in Samsung My Files, published on 6 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper export of Android application components in My Files prior to version 15.0.07.5 in Android 14 allows local attackers to access files with My Files' privilege.

## Which versions are affected by CVE-2025-20926?

It affects 1 product.


Products: Samsung Myfiles.

## How do I fix CVE-2025-20926?

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

## Is CVE-2025-20926 being exploited?

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

## Other vulnerabilities in Samsung My Files

- [CVE-2023-21463](https://insights.sbomify.com/CVE-2023-21463/): Information disclosure in MyFiles (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-20926 and fix it if it is affected.

What it is: CVE-2025-20926 is a medium-severity missing authorization vulnerability in Samsung My Files, published on 6 Mar 2025. 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-2025-20926 in the wild and no public exploit code.

Affected product: Samsung My Files. 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-2025-20926/ (Markdown: https://insights.sbomify.com/CVE-2025-20926/index.md)
```

## Sources

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

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