# CVE-2026-81301: Ekia File Manager 1.2.7 - Exported ContentProvider allows unauthorized file access

> A local attacker can read, modify, or delete files via an exported ContentProvider in Ekia File Manager due to missing permission checks and path validation.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-jjh4-j2rc-jqhg

## What is CVE-2026-81301?

CVE-2026-81301 is a high-severity path traversal vulnerability in Ekia File Manager, published on 14 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Ekia File Manager 1.2.7 exposes com.ekia.filecontrolmanager.OpenFileProvider as an exported Android ContentProvider without requiring caller permissions.

The provider maps the caller-controlled URI path directly to a filesystem path and passes it to new File(...). It then supports query(), openFile(), and delete() operations. Because the provider is exported and lacks android:permission, android:readPermission, or android:writePermission, another local application can access the provider authority and cause File Manager's process to read, create, overwrite, or delete files that are accessible to that process.

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

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


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

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

## Is CVE-2026-81301 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-81301 is a high-severity path traversal vulnerability in Ekia File Manager, published on 14 Sep 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-81301 in the wild and no public exploit code.

Affected product: Ekia File Manager. 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-81301/ (Markdown: https://insights.sbomify.com/CVE-2026-81301/index.md)
```

## Sources

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

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