# CVE-2025-14111: Rarlab RAR App com.rarlab.rar path traversal

> Attackers can exploit a path traversal flaw in RAR for Android to read or modify files outside the intended directory.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Dec 2025
- **Updated:** 8 Dec 2025
- **Also known as:** GHSA-446c-49cw-x44x

## What is CVE-2025-14111?

CVE-2025-14111 is a low-severity path traversal vulnerability in Rarlab RAR App, published on 5 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A security vulnerability has been detected in Rarlab RAR App up to 7.11 Build 127 on Android. This affects an unknown part of the component com.rarlab.rar. Such manipulation leads to path traversal. It is possible to launch the attack remotely. Attacks of this nature are highly complex. It is indicated that the exploitability is difficult. The exploit has been disclosed publicly and may be used. Upgrading to version 7.20 build 128 is able to mitigate this issue. You should upgrade the affected component. The vendor responded very professional: "This is the real vulnerability affecting RAR for Android only. WinRAR and Unix RAR versions are not affected. We already fixed it in RAR for Android 7.20 build 128 and we publicly mentioned it in that version changelog. (...) To avoid confusion among users, it would be useful if such disclosure emphasizes that it is RAR for Android only issue and WinRAR isn't affected."

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Rarlab Rar.

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

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

## Is CVE-2025-14111 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-14111 exists.

## Other vulnerabilities in Rarlab RAR App

- [CVE-2014-9983](https://insights.sbomify.com/CVE-2014-9983/): Path traversal in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14111 is a low-severity path traversal vulnerability in Rarlab RAR App, published on 5 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-14111 exists.

Affected product: Rarlab RAR App. 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-14111/ (Markdown: https://insights.sbomify.com/CVE-2025-14111/index.md)
```

## Sources

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

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