CVE-2025-14111VulnerabilityPublished 5 Dec 2025Updated 8 Dec 2025

CVE-2025-14111: Rarlab RAR App · Path Traversal

Affects Rarlab RAR AppSource CVE Database V5

Not known to be exploited · CVSS 2.3 Low · fixed in 7.20 : update Rarlab RAR App when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

2.3Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 7.20

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

Base metrics

Attack Vector: Network
Attack Complexity: High
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

European organizations should implement the following specific mitigation measures: 1) Immediately upgrade all instances of the Rarlab RAR App on Android devices to version 7.20 Build 128 or later to eliminate the vulnerability. 2) Enforce mobile device management (MDM) policies that restrict installation of outdated or unapproved app versions and enable centralized patch management. 3) Educate users about the risks of opening archive files from untrusted sources, emphasizing caution with unsolicited or suspicious archives. 4) Monitor network traffic and device logs for unusual file extraction activities or attempts to write files outside expected directories. 5) Employ endpoint protection solutions capable of detecting anomalous file system operations on mobile devices. 6) Where possible, limit the use of third-party archiving apps in favor of built-in or vetted alternatives with a strong security track record. 7) Conduct regular security audits of mobile applications and update policies to include rapid response to disclosed vulnerabilities. These steps go beyond generic advice by focusing on organizational controls, user awareness, and proactive patch enforcement tailored to the mobile environment.

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."

Impact

For European organizations, the impact of CVE-2025-14111 is generally low due to the complexity of exploitation and the limited scope of the vulnerability affecting only the Android RAR app. However, organizations that rely heavily on mobile devices for file archiving and extraction, especially those handling sensitive or critical data on Android platforms, could face risks of unauthorized file overwrites or data manipulation. This could lead to localized data integrity issues or facilitate further attacks if malicious files are placed in strategic locations. The vulnerability does not compromise confidentiality directly but can affect integrity and availability at a low level. Given the widespread use of Android devices in Europe, especially in sectors like finance, healthcare, and government, there is a potential for targeted attacks if threat actors craft malicious archives to exploit this flaw. The absence of known exploits in the wild and the availability of a patch reduce the overall risk, but delayed patching could increase exposure.

Summary

CVE-2025-14111 is a path traversal vulnerability identified in the Rarlab RAR App for Android, specifically affecting versions up to 7.11 Build 127. The vulnerability resides in the component com.rarlab.rar, where improper validation of file paths during archive extraction allows an attacker to traverse directories and write files outside the intended extraction folder. This can lead to overwriting or creating files in arbitrary locations on the device's filesystem, potentially compromising data integrity or enabling further malicious actions. The attack vector is remote, but exploitation is complex, requiring user interaction (e.g., opening a crafted archive). The CVSS 4.0 vector indicates network attack vector (AV:N), high attack complexity (AC:H), no privileges required (PR:N), user interaction required (UI:P), and low impact on confidentiality, integrity, and availability (each rated low). The vendor has confirmed that this vulnerability affects only the Android version of the RAR app, not the Windows or Unix versions, and has released a fix in version 7.20 Build 128. No known exploits are currently observed in the wild, and the exploitability is considered difficult. The vulnerability's public disclosure emphasizes the need for users to upgrade to the patched version to mitigate risk.

References

Community reviews

Loading reviews…