# CVE-2025-2091: Open redirection in M-Files Mobile

> Attackers can trick users into visiting malicious URLs via crafted PDFs in M-Files Mobile, requiring an upgrade to secure the application.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/RE:M/U:Green`)
- **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:** 16 Jun 2025
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-525r-jw95-mh3f

## What is CVE-2025-2091?

CVE-2025-2091 is a medium-severity vulnerability in M-Files Mobile, published on 16 Jun 2025. 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 open redirection vulnerability in M-Files mobile applications for Android and iOS prior to version 25.6.0 allows attackers to use maliciously crafted PDF files to trick other users into making requests to untrusted URLs.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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

It affects 1 product.


Products: M-Files M-Files Mobile.

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

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

## Is CVE-2025-2091 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2091 is a medium-severity vulnerability in M-Files Mobile, published on 16 Jun 2025. 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-2091 in the wild and no public exploit code.

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

## Sources

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

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