# CVE-2025-68713: Path traversal in n/a

> Untrusted apps can force arbitrary file downloads into the app's storage, potentially leading to code execution or denial of service.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 16 Jun 2026
- **Also known as:** GHSA-5jv9-6p43-2v8w

## What is CVE-2025-68713?

CVE-2025-68713 is a high-severity path traversal vulnerability in n/a, published on 15 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in Rakuten Send Anywhere (File Transfer) for Android (com.estmob.android.sendanywhere) 23.2.9. The vulnerability allows untrusted applications (with no permissions) to force arbitrary file downloads into the app's scoped storage. The resulting files appear in the application's trusted Received interface. These conditions establish a vector for arbitrary code execution if the payload is an APK file, or a denial-of-service condition through resource exhaustion from oversized transfers.

Weakness: CWE-926 (Improper Export of Android Application Components)

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


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

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

## Is CVE-2025-68713 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-68713 is a high-severity path traversal vulnerability in n/a, published on 15 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-68713 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-2025-68713/ (Markdown: https://insights.sbomify.com/CVE-2025-68713/index.md)
```

## Sources

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

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